Date:	Sun, 26 Sep 1999 08:12:25 +0200 (IST)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender:	eliz AT is
To:	GAMMELJL AT SLU DOT EDU
cc:	djgpp AT delorie DOT com
Subject:	Re: problem with new malloc.c attn: Eli Zaretskii
In-Reply-To:	<01JGBS3N1LOI9I4DA5@SLU.EDU>
Message-ID:	<Pine.SUN.3.91.990926080947.17688H-100000@is>
MIME-Version:	1.0
Reply-To:	djgpp AT delorie DOT com
X-Mailing-List:	djgpp AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On Thu, 23 Sep 1999 GAMMELJL AT SLU DOT EDU wrote:

>      It looks very much like the last screen which I symified and posted.
> Any thoughts?

It indeed looks like a problem with overwritten buffer allocated by 
malloc or new.

If the address where it crashes is constant, and so are the registers 
printed in the crash message, you could try running under a debugger and
putting a data-write breakpoint at the address that is being overwritten.
Then the debugger will catch the offending code red-handed.  Section 12.2 
of the FAQ tells you more about this.

Another alternative is to download YAMD and let it find the villain.

- Raw text -