Subject: Re: realloc SEGV
To: None <email@example.com>
From: Brett Lymn <firstname.lastname@example.org>
Date: 08/28/1999 21:59:29
According to email@example.com:
>I generally "solve" this by replacing malloc and realloc with wrapper
>functions which log all allocations and frees, then run until the crash,
>then run a little perl script on the output to find out what memory was
>freed twice, or what memory was freed that was never allocated, etcetera.
Or where the bounds of a malloc'ed region have been overflowed -
always a good one for producing a crash a few malloc's later. There
is a library called electric fence IIRC that helps with this bug.
Brett Lymn, Computer Systems Administrator, British Aerospace Australia