Nagatoro skrev:
> On Tuesday 10 November 2009 13.14.13 Alan McKinnon wrote:
> [...]
>   
>> *** glibc detected *** amarok: free(): invalid pointer: 0x0000000003295080
>>  ***
>>     
>
> This is a highly debated issue, glibc has new checks for various things and 
> it 
> seems like some think the checks are to strict or even wrong while others 
> think that the checks are ok and the applications are wrong.
>   
Really? A pointer is valid for free() if it has been returned by malloc,
calloc, realloc or strdup, and has not yet been passed to free(). What
could there possibly be to debate?

Reply via email to