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 1210 - SDL_Quit causes an exit(234) in fglrx_dri.so
Summary: SDL_Quit causes an exit(234) in fglrx_dri.so
Status: RESOLVED INVALID
Alias: None
Product: SDL
Classification: Unclassified
Component: video (show other bugs)
Version: HG 2.0
Hardware: x86_64 Linux
: P2 normal
Assignee: Sam Lantinga
QA Contact: Sam Lantinga
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-05-23 13:07 UTC by Pierre Bourdon
Modified: 2015-02-18 03:28 UTC (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Pierre Bourdon 2011-05-23 13:07:03 UTC
When using SDL 1.3 with fglrx (ATI proprietary driver), SDL_Quit causes the driver to call exit with error code 234. Call trace:

#0  0x00007ffff75e4290 in exit () from /lib/libc.so.6
#1  0x00007ffff4cadf1c in ?? () from /usr/lib/xorg/modules/dri//fglrx_dri.so
#2  0x00007ffff4cac64d in ?? () from /usr/lib/xorg/modules/dri//fglrx_dri.so
#3  0x00007ffff4d05639 in ?? () from /usr/lib/xorg/modules/dri//fglrx_dri.so
#4  0x00007ffff4d018a4 in ?? () from /usr/lib/xorg/modules/dri//fglrx_dri.so
#5  0x00007ffff43ffd9f in ?? () from /usr/lib/xorg/modules/dri//fglrx_dri.so
#6  0x00007ffff4400d00 in ?? () from /usr/lib/xorg/modules/dri//fglrx_dri.so
#7  0x00007ffff43aa599 in ?? () from /usr/lib/xorg/modules/dri//fglrx_dri.so
#8  0x00007ffff43f80c3 in ?? () from /usr/lib/xorg/modules/dri//fglrx_dri.so
#9  0x00007ffff4379c7d in ?? () from /usr/lib/xorg/modules/dri//fglrx_dri.so
#10 0x00007ffff4233e0c in ?? () from /usr/lib/xorg/modules/dri//fglrx_dri.so
#11 0x00007ffff378b8e2 in ?? () from /usr/lib/xorg/modules/dri//fglrx_dri.so
#12 0x00007ffff3807c84 in ?? () from /usr/lib/xorg/modules/dri//fglrx_dri.so
#13 0x00007ffff4217c3d in ?? () from /usr/lib/xorg/modules/dri//fglrx_dri.so
#14 0x00007ffff4ca71b7 in ?? () from /usr/lib/xorg/modules/dri//fglrx_dri.so
#15 0x00007ffff4ca7631 in ?? () from /usr/lib/xorg/modules/dri//fglrx_dri.so
#16 0x00007ffff4ca76e7 in ?? () from /usr/lib/xorg/modules/dri//fglrx_dri.so
#17 0x00007ffff7945b89 in ?? () from /usr/lib/libGL.so.1
#18 0x00007ffff7945bca in ?? () from /usr/lib/libGL.so.1
#19 0x00007ffff69def25 in _XFreeExtData () from /usr/lib/libX11.so.6
#20 0x00007ffff69ec6a8 in _XFreeDisplayStructure () from /usr/lib/libX11.so.6
#21 0x00007ffff69d868f in XCloseDisplay () from /usr/lib/libX11.so.6
#22 0x00007ffff7ba7106 in X11_DeleteDevice (device=0x608360) at src/video/x11/SDL_x11video.c:109
#23 0x00007ffff7b9a730 in SDL_VideoQuit () at src/video/SDL_video.c:2078
#24 0x00007ffff7b20c25 in SDL_QuitSubSystem (flags=<value optimized out>) at src/SDL.c:192
#25 0x00007ffff7b20cde in SDL_Quit () at src/SDL.c:214
#26 0x00000000004006f0 in main ()

Test case:

#include <SDL/SDL.h>

int main(void)
{
    SDL_Init(SDL_INIT_VIDEO);
    SDL_SetVideoMode(640, 480, 0, SDL_OPENGL);

    SDL_Quit();
    return 0;
}

This does not happen with SDL 1.2, and bisecting showed that the bug was introduced when the X11 driver code was rewritten (around r1953).
Comment 1 Pierre Bourdon 2011-05-23 13:34:52 UTC
A friend which also has an ATI card and uses fglrx just confirmed that this bug occurs on his computer. Also, X displays this error message before exiting :

XIO:  fatal IO error 11 (Resource temporarily unavailable) on X server "pZ�"
      after 281 requests (281 known processed) with 0 events remaining.

I sometimes had such error messages too when testing on my machine, so I think it is more or less random. Note the corrupted X server name.
Comment 2 Ozkan Sezer 2011-06-14 00:33:56 UTC
Possibly related: bug #1120.  Although it is closed as invalid, I'm not really convinced about it at all.
Comment 3 Sam Lantinga 2013-05-21 02:40:58 UTC
Is this bug still active with the latest snapshot?
http://www.libsdl.org/tmp/SDL-2.0.zip

Thanks!
Comment 4 Ryan C. Gordon 2015-02-18 03:28:13 UTC
Assuming this was a driver bug and resolving. Please reopen if you're still having this problem.

--ryan.