We are currently migrating Bugzilla to GitHub issues.
Any changes made to the bug tracker now will be lost, so please do not post new bugs or make changes to them.
When we're done, all bug URLs will redirect to their equivalent location on the new bug tracker.

Bug 4089

Summary: SDL_CreateThread crash
Product: SDL Reporter: Anta999 <arcticshine999>
Component: threadAssignee: Ryan C. Gordon <icculus>
Status: RESOLVED INVALID QA Contact: Sam Lantinga <slouken>
Severity: normal    
Priority: P2 CC: icculus
Version: 2.0.7   
Hardware: x86_64   
OS: Windows 7   

Description Anta999 2018-02-21 18:29:39 UTC
call to SDL_CreateThread couse crash  Exception: Access violation
Comment 1 Anta999 2018-02-21 18:30:31 UTC
I'm go down to SDL 2.0.4 now
Comment 2 Ryan C. Gordon 2018-02-21 18:43:19 UTC
(In reply to Anta999 from comment #1)
> I'm go down to SDL 2.0.4 now

Often times this is because SDL thinks a debugger is attached and tries to name the thread, but that should be disabled in 2.0.7. Can you tell us where it's crashing, specifically, inside SDL_CreateThread?

--ryan.
Comment 3 Anta999 2018-02-21 19:04:27 UTC
(In reply to Ryan C. Gordon from comment #2)
> (In reply to Anta999 from comment #1)
> > I'm go down to SDL 2.0.4 now
> 
> Often times this is because SDL thinks a debugger is attached and tries to
> name the thread, but that should be disabled in 2.0.7. Can you tell us where
> it's crashing, specifically, inside SDL_CreateThread?
> 
> --ryan.

Sorry. After recompile with new headers(from 2.0.7) no more crash!
Thanks for reply!
Comment 4 Anta999 2018-02-21 19:13:03 UTC
(In reply to Ryan C. Gordon from comment #2)
> (In reply to Anta999 from comment #1)
> > I'm go down to SDL 2.0.4 now
> 
> Often times this is because SDL thinks a debugger is attached and tries to
> name the thread, but that should be disabled in 2.0.7. Can you tell us where
> it's crashing, specifically, inside SDL_CreateThread?
> 
> --ryan.

I think it was a dynapi, it was off in my old SDL version
Comment 5 Ryan C. Gordon 2018-02-22 04:50:17 UTC
Ok, cool, glad it's working for you now!

--ryan.