We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
access violation, during initialization of sdl-freerdp (x64) on windows (build 1448) downloaded here: https://ci.freerdp.com/job/freerdp-nightly-windows/
Steps to reproduce the behavior: just launch exe
Additional context kind of stack trace (if correctly compiled ...)
SDL_bool SDL_RemoveTimer(SDL_TimerID id) { SDL_TimerData *data = &SDL_timer_data;
SDL_timer_data is null...
0000000000000000() SDL2d.dll!SDL_LockMutex_REAL(SDL_mutex * mutex) Line 286 SDL2d.dll!SDL_RemoveTimer_REAL(int id) Line 347 SDL2d.dll!SDL_RemoveTimer(int a) Line 520 sdl-freerdp.exe!sdlDispContext::addTimer() Line 297 sdl-freerdp.exe!sdlDispContext::sdlDispContext(SdlContext * sdl) Line 454 sdl-freerdp.exe!SdlContext::SdlContext(rdp_context * context) Line 1680 sdl-freerdp.exe!sdl_client_new(rdp_freerdp * instance, rdp_context * context) Line 1398 sdl-freerdp.exe!freerdp_client_common_new(rdp_freerdp * instance, rdp_context * context) Line 94 sdl-freerdp.exe!freerdp_context_new_ex(rdp_freerdp * instance, rdp_settings * settings) Line 845 sdl-freerdp.exe!freerdp_client_context_new(const rdp_client_entry_points_v1 * pEntryPoints) Line 135 sdl-freerdp.exe!SDL_main(int argc, char * * argv) Line 1605 sdl-freerdp.exe!main_getcmdline() Line 80 sdl-freerdp.exe!WinMain(HINSTANCE__ * hInst, HINSTANCE__ * hPrev, char * szCmdLine, int sw) Line 110 [External Code]
Thank you for reporting a bug!
The text was updated successfully, but these errors were encountered:
[client,SDL] check for timer initialized
223b471
before manipulating SDL timers check if the SDL subsystem was actually initialized. Fixes FreeRDP#9736
a45e464
before manipulating SDL timers check if the SDL subsystem was actually initialized. Fixes #9736
akallabeth
Successfully merging a pull request may close this issue.
access violation, during initialization of sdl-freerdp (x64) on windows (build 1448)
downloaded here: https://ci.freerdp.com/job/freerdp-nightly-windows/
Steps to reproduce the behavior:
just launch exe
Additional context
kind of stack trace (if correctly compiled ...)
SDL_bool SDL_RemoveTimer(SDL_TimerID id)
{
SDL_TimerData *data = &SDL_timer_data;
SDL_timer_data is null...
Thank you for reporting a bug!
The text was updated successfully, but these errors were encountered: