Hello,
this is about a crash/debug breakage for the current SDL 1.2
source tree (today’s svn checkout, same problem in 1.2.13 and
before as far as relevant).
In some places memory is free()d but the associated pointer
is not zeroed, leading to for example double free()s.
For me this happened because SDL_StopEventThread() was executed
twice (during restart of the subsystems), once for the close
down in SDL_VideoQuit() and once at the startup, right at the
beginning of SDL_StartEventLoop(). Thus the code
SDL_DestroyMutex(SDL_EventQ.lock);
(see SDL_events.c) was called twice and executed the
SDL_free(mutex);
twice as well, leading to a crash (msvc 64bit for which it was
noticed).
I’ve tried to check all other occurrences of SDL_free and similar
code in msvc, see the attached patch (udiff against revision 4082).
Non-windows only codepaths have neither been checked nor touched.
Comments/ideas welcome.
Attached patch: NULLifies some pointers after they
have been free()d.
-------------- next part --------------
A non-text attachment was scrubbed…
Name: sdl12_dblfree.diff
Type: application/octet-stream
Size: 2770 bytes
Desc: not available
URL: http://lists.libsdl.org/pipermail/sdl-libsdl.org/attachments/20080907/fe5429fb/attachment.obj