[SDL] SDL Digest, Vol 12, Issue 32

James Barrett xucaen at gmail.com
Wed Dec 26 10:27:02 PST 2007


The tool reports a LOT of memory leaks and errors in libsdl. How
accurate is this tool?
Does this tool report deleting a null pointer as an error? Looks like it
might be even though it shouldn't, but I'm having a hard time reading
through all of the output.

Clemens Kirchgatterer wrote:
> James Barrett <xucaen at gmail.com> wrote:
>
>   
>> renjith kumar wrote:
>>     
>>>  *** glibc detected *** ./sample: free(): invalid pointer:
>>> 0xbf8242b8 ***
>>>       
>  
>   
>> I get this same error when my program exits. I've been ignoring it
>> because I thought maybe SDL_FreeSurface (or some other sdl free
>> function) was getting called more than once for the same pointer.
>>     
>
> ignoring it is not very good practice, you have a bug in your code that
> might come back at some later time and bite you.
>
> i suggest the usage of valgrind (for both of you).
>
> best regards ...
> clemens




More information about the SDL mailing list