Access violation in SDL_RenderCopy

I just got a bug report from a user.? The error logging tool gave me a stack trace, but the top of the stack was missing since the error happened inside of SDL_RenderCopy.? The message text was “Access violation at address 6F4635C5 in module ‘SDL2.dll’. Read of address 62617475.”

That read address tells me that it’s not trying to read a null pointer; something somewhere is trying to read a garbage value.? Unfortunately, this isn’t reproducible locally, and no one else who uses the program (with the same build of SDL2) reports the same error.

Has anyone seen SDL raise exceptions like that?? The user says he’s running Win7, 64-bit, which is the same OS I have.? Any ideas how I’d go about tracking down something like this?

Mason

2013/4/8 Mason Wheeler

I just got a bug report from a user. The error logging tool gave me a
stack trace, but the top of the stack was missing since the error happened
inside of SDL_RenderCopy. The message text was “Access violation at
address 6F4635C5 in module ‘SDL2.dll’. Read of address 62617475.”

That read address tells me that it’s not trying to read a null pointer;
something somewhere is trying to read a garbage value. Unfortunately, this
isn’t reproducible locally, and no one else who uses the program (with the
same build of SDL2) reports the same error.

Has anyone seen SDL raise exceptions like that? The user says he’s
running Win7, 64-bit, which is the same OS I have. Any ideas how I’d go
about tracking down something like this?

Mason


SDL mailing list
SDL at lists.libsdl.org
http://lists.libsdl.org/listinfo.cgi/sdl-libsdl.org

Are you using Render Targets? Software, Direct3D or OpenGL backend? Can you
tell if RenderCopy enters the “backend” function?–
Gabriel.