No description
17e16c2e64
felix
Here's a snippet of SDL_DestroyRenderer from hg revision 10746:95c57a177719:
SDL_Texture *texture = NULL;
SDL_Texture *nexttexture = NULL;
/* ... */
for (texture = renderer->textures; texture; texture = nexttexture) {
nexttexture = texture->next;
SDL_DestroyTexture(texture);
}
SDL_DestroyTexture removes the texture from the linked list pointed to by the renderer and ends up calling SDL_DestroyTextureInternal, which contains this:
if (texture->native) {
SDL_DestroyTexture(texture->native);
}
If it happens that texture->native is an alias of nexttexture two stack frames up, SDL_DestroyRenderer will end up trying to destroy an already freed texture. I've had this very situation happen in dosemu2.
Bug introduced in revision 10650:b6ec7005ca15, which has a somewhat ironic description of "Fixed all known static analysis bugs"...
|
||
|---|---|---|
| acinclude | ||
| android-project | ||
| build-scripts | ||
| cmake | ||
| debian | ||
| docs | ||
| include | ||
| src | ||
| test | ||
| VisualC | ||
| VisualC-WinRT | ||
| visualtest | ||
| Xcode | ||
| Xcode-iOS | ||
| .hgignore | ||
| .hgtags | ||
| Android.mk | ||
| autogen.sh | ||
| BUGS.txt | ||
| cmake_uninstall.cmake.in | ||
| CMakeLists.txt | ||
| configure | ||
| configure.in | ||
| COPYING.txt | ||
| CREDITS.txt | ||
| INSTALL.txt | ||
| Makefile.in | ||
| Makefile.minimal | ||
| Makefile.pandora | ||
| Makefile.psp | ||
| Makefile.wiz | ||
| README-SDL.txt | ||
| README.txt | ||
| sdl2-config.cmake.in | ||
| sdl2-config.in | ||
| sdl2.m4 | ||
| sdl2.pc.in | ||
| SDL2.spec.in | ||
| TODO.txt | ||
| VisualC.html | ||
| WhatsNew.txt | ||
Simple DirectMedia Layer
(SDL)
Version 2.0
---
http://www.libsdl.org/
Simple DirectMedia Layer is a cross-platform development library designed
to provide low level access to audio, keyboard, mouse, joystick, and graphics
hardware via OpenGL and Direct3D. It is used by video playback software,
emulators, and popular games including Valve's award winning catalog
and many Humble Bundle games.
More extensive documentation is available in the docs directory, starting
with README.md
Enjoy!
Sam Lantinga (slouken@libsdl.org)