On Wed, 13 Jun 2007 17:31:17 -0400 Dennis Schridde <[EMAIL PROTECTED]> wrote: >Am Mittwoch, 13. Juni 2007 schrieb [EMAIL PROTECTED]: >> The game crash on that line, free(image->bmp). >> Since it set to NULL after 1st free call, we can then assume >that >> image pointer is wrong/corrupted. >> So then fix is to find where image is free, and make sure is set >to >> NULL? >So the problem is not that image->bmp is already freed, but that >image was >freed somewhere before we want to free image->bmp? >That's ugly and should be fixed, instead of checking for bmp being >null... > >Can you please provide a backtrace or tell us who tried to unload >an image >twice? > >Besides that: >frameresource.c:667 might be the cause and should be investigated. > Yes, next time crash @ that point, I will post stack dump.
-- Click here for self-employed health insurance. Compare quotes for free! http://tagline.hushmail.com/fc/CAaCXv1KdvbID6M83HGOk7Ts3FLbUkYv/ _______________________________________________ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev
