From:	sandmann AT clio DOT rice DOT edu (Charles Sandmann)
Message-Id:	<9907061440.AA15007@clio.rice.edu>
Subject:	Re: Re: gcc-crash - and a possible solution
To:	eliz AT is DOT elta DOT co DOT il (Eli Zaretskii)
Date:	Tue, 6 Jul 1999 09:40:02 -0600 (CDT)
Cc:	erik2 DOT berglund AT telia DOT com, djgpp-workers AT delorie DOT com, pavenis AT lanet DOT lv
In-Reply-To:	<Pine.SUN.3.91.990706130902.17419E-100000@is> from "Eli Zaretskii" at Jul 6, 99 01:12:35 pm
X-Mailer:	ELM [version 2.4 PL20]
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

> If you mean two DOS boxes with *any* DJGPP programs, not necessarily GCC, 
> then I always do that.  On my office machine, running Windows 95, there's 
> always one DOS box with Emacs, another with Info, and I use two other for 
> command-line tasks, including compiling programs.  I never had any 
> crashes in CC1 like what you see.

To get the 3.9Gb addresses you must exit an application run earlier (so it
frees it's memory which is typically lower addresses) and then have an
application still running allocate more new memory.

The sorts of things that broke some applications:

 0-1Mb space, then sbrk returns 3.9Gb block (broke signed/unsigned)
 0-1Mb space, sbrk returns 3.9Gb address, then sbrk returns 1Mb address
       (this broke some assumptions in some code about sbrk always 
        increasing)

It may be the second case which is biting malloc and/or CC1.

- Raw text -