From:	pavenis AT lanet DOT lv
Message-ID:	<B0000115672@stargate.astr.lu.lv>
To:	jazir <entropic AT mpx DOT com DOT au>, djgpp AT delorie DOT com
Date:	Thu, 13 Jan 2000 18:43:35 +0200
MIME-Version:	1.0
Subject:	Re: upgrade chaos
In-reply-to:	<387D90EF.1D5B0DCB@mpx.com.au>
X-mailer:	Pegasus Mail for Win32 (v3.12b)
Reply-To:	djgpp AT delorie DOT com
Errors-To:	dj-admin AT delorie DOT com
X-Mailing-List:	djgpp AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On 13 Jan 00, at 19:46, jazir wrote:

> 
> 
> Eli Zaretskii wrote:
> > 
> > On Wed, 12 Jan 2000, jazir wrote:
> > 
> > >   i'm willing to accept that my code is buggy, so i'll do
> > > my best at finding it.  however, it was v2.02 that i upgraded
> > > from.
> > 
> > Then it is a little bit less evident, but I cannot really tell without
> > seeing the full crash message.  Can you post it?
> 
> Yep I can do that.  Firstly I'd like to say that YAMD is a great program,
> as it helped me find memory leaks...but there were no msg'es about accessing
> memory not belonging to my program.  Once I had the leaks sorted, the only
> output was for successful allocation and deallocation of blocks.
> 
> In fact, when I compiled my program with YAMD, everything worked as expected.
> There was no crash..that could just mean that my bug goes back to doing no
> damage, as in djgpp v2.02, but YAMD should still detect it... i'm puzzled.
> 
> Here is the symify'ed output for two different runs {compressing different 
> files}.  As you can see, one GPF occurs in malloc, the other in free.
> 

You may also try fortify.

http://www.geocities.com/SiliconValley/Horizon/8596/fortify.html

A rather long time ago it helped me to catch bug in rhide-1.4 by 
writting one byte beyond allocated memory which caused crash in
debugger much later.

- Raw text -