Date:	Sun, 20 Jun 1999 10:56:28 +0300 (IDT)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender:	eliz AT is
To:	Andris Pavenis <pavenis AT ieva01 DOT lanet DOT lv>
cc:	Erik Berglund <erik2 DOT berglund AT telia DOT com>, djgpp-workers AT delorie DOT com
Subject:	Re: Re: gcc-crash - and a possible solution
In-Reply-To:	<Pine.A41.4.05.9906191130080.92922-100000@ieva01.lanet.lv>
Message-ID:	<Pine.SUN.3.91.990620105547.16821P-100000@is>
MIME-Version:	1.0
Reply-To:	djgpp-workers AT delorie DOT com
X-Mailing-List:	djgpp-workers AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

> In my humble opinion, it would be easiest to reproduce and track down
> the error, if we modify gcc-2.95 to catch any DPMI-errors and such.

I find it hard to believe that a DPMI server problem can cause these
crashes.  Note that the crash is inside `free', not inside `malloc' or
any other code that uses `malloc'ed buffer.  If the problem lies with
the allocation of memory, then either `malloc' should have crashed, or
some code that uses the allocated buffer.

No, this problem seems to be with how allocated memory is used by the
program.  It might be triggered by some special (mis)-behavior of the
Windows 3.X DPMI server, but I don't think it is directly connected
with it.

- Raw text -