Date:	Tue, 22 Jun 1999 09:24:28 +0300 (IDT)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender:	eliz AT is
To:	Erik Berglund <erik2 DOT berglund AT telia DOT com>
cc:	pavenis AT lanet DOT lv, djgpp-workers AT delorie DOT com
Subject:	Re: Re: gcc-crash - and a possible solution
In-Reply-To:	<MAPI.Id.0016.00333138303633303030303930303039@MAPI.to.RFC822>
Message-ID:	<Pine.SUN.3.91.990622092333.25569F-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

On Mon, 21 Jun 1999, Erik Berglund wrote:

> Anyway, just for testing, I changed my 4 EDO-RAMs (32 Mbyte each)
> to 2 older Parity-RAMs (8 Mbyte each), but I still got error messages,
> however different (Abort!).

Where (from which function) did that "Abort!" come from?  Is it coming
from GCC code or from the library?

IIRC, `malloc' from DJGPP v2.01 called `abort' (which printed
"Abort!") when it thought it was botched.  The version of `malloc'
from v2.02 doesn't do that.  Which library did you use to build GCC?

Another place in the library that calls `abort' is the function that
passes file names to DOS system calls.

- Raw text -