[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: Detecting Seg faults

To: linuxgames@sunsite.dk
Subject: Re: Detecting Seg faults
From: "Adam D. Moss" <adam@gimp.org>
Date: Tue, 19 Oct 2004 17:23:04 +0100
Delivered-to: archiver@seul.org
Delivered-to: mailing list linuxgames@sunsite.dk
Delivery-date: Tue, 19 Oct 2004 12:22:23 -0400
In-reply-to: <200410191821.45125.xarvh@lombardiacom.it>
Mailing-list: contact linuxgames-help@sunsite.dk; run by ezmlm
References: <200410191821.45125.xarvh@lombardiacom.it>
Reply-to: linuxgames@sunsite.dk
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.4) Gecko/20041013

Francesco Orsenigo wrote:

How can i find the point where the bad dereference happens, if the program is not crashing there?
Is there a way to force a more strict memory check?

First thing to do if you suspect heap corruption is

setenv MALLOC_CHECK_ 2

- then the heap allocator does a lot more sanity checking
and you get an abort as soon as something looks strange.
This is a real lifesaver while developing.

If that doesn't help with random crashes and the code looks
sane then I'd usually reach for Valgrind...

--Adam

References:
- Detecting Seg faults
  - From: Francesco Orsenigo <xarvh@lombardiacom.it>

Prev by Author: code: x-platform locale detection
Next by Author: Re: code: x-platform locale detection
Previous by thread: Detecting Seg faults
Next by thread: Re: Detecting Seg faults
Index(es):
- Author
- Thread