[SDL] SDL/win32 incompatible with fprintf(stderr,...) atexit?

Neil Griffiths n.griffiths at virgin.net
Sat Sep 21 14:31:01 PDT 2002


If the destructor calls fprintf() after you've called SDL_Quit() then
you may get this behavior. You should delete your objects before the
end of the program anyway instead of expecting the program to clean up
after itself - it's good programming practice to deallocate any memory
you allocate.


Saturday, September 21, 2002, 9:04:26 PM, you wrote:

TH> The title more or less gives my question away. I am trying to use SDL with
TH> another library, which is in the habit of fprintf'ing to stderr as part of
TH> the atexit functionality. Well, I think it might be part of a destructor in
TH> a globally declared class, but whatever.

TH> The program crashes inside the call to fprintf. I thought perhaps this might
TH> be due to SDLMain, and its habit of creating a stderr.txt for me, and then
TH> closing it later on. Otherwise the problem is something much more ominous.
TH> Does this diagnosis sound likely? If so, can anyone think of any way
TH> whatsoever to provide a stderr for this other library?

TH> -Thomas

TH> _______________________________________________
TH> SDL mailing list
TH> SDL at libsdl.org
TH> http://www.libsdl.org/mailman/listinfo/sdl

Best regards,
 Neil                            mailto:n.griffiths at virgin.net

More information about the SDL mailing list