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 645

Summary: Usually locks up when there's an error
Product: SDL Reporter: Tony Houghton <h>
Component: *don't know*Assignee: Ryan C. Gordon <icculus>
Status: RESOLVED INVALID QA Contact: Sam Lantinga <slouken>
Severity: normal    
Priority: P2 CC: bombasticbryan
Version: 1.2.13Keywords: target-1.2.14
Hardware: x86   
OS: Linux   

Description Tony Houghton 2008-11-25 16:18:24 UTC 
Most SDL errors cause the application to hang until it's sent a KILL signal. Why can't it exit() or abort() instead?
Comment 1 Ryan C. Gordon 2009-09-13 16:33:20 UTC 
Tagging this bug with "target-1.2.14" so we can try to resolve it for SDL 1.2.14.

Please note that we may choose to resolve it as WONTFIX. This tag is largely so we have a comprehensive wishlist of bugs to examine for 1.2.14 (and so we can close bugs that we'll never fix, rather than have them live forever in Bugzilla).

--ryan.
Comment 2 Sam Lantinga 2009-09-21 03:56:10 UTC 
SDL tries to cleanly shut down the video system, because if it doesn't it can render the system unusable in fullscreen mode.

Can you attach gdb when it's hung and get a stack trace to see where it's stuck?

What kind of SDL errors are causing the problem?
Comment 3 Tony Houghton 2009-09-23 12:11:30 UTC 
Sorry it's a fairly useless bug report. I just got the impression that this seemeed to happen with more than one SDL program, but I can't remember what now. I think I found one case where one or more threads were left running when one critical thread had died, so perhaps there isn't a problem with SDL, just poor multithreaded error handling in applications.
Comment 4 Sam Lantinga 2009-09-24 00:31:16 UTC 
Okay, thanks for the info!