Date: Sun, 14 Apr 1996 09:00:48 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: Hans-Bernhard Broeker <Broeker AT axp03 DOT physik DOT rwth-aachen DOT de>
Cc: djgpp AT delorie DOT com
Subject: Re: malloc crash
In-Reply-To: <Broeker.829229550@axp03>
Message-Id: <Pine.SUN.3.91.960414085602.1640O-100000@is>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


On 11 Apr 1996, Hans-Bernhard Broeker wrote:

> Well, I'm not sure if this is really related, but some weeks ago I had
> problems to compile one specific source file (part of gnuplot 3.6) with
> "-O3 -Wall -W" flags enabled (cc1 produced a seg fault).  After some
> tracking down, I finally managed to 'solve' this by rebuilding gcc and
> using the GNU malloc package (the offending line inside cc1 was actually
> a call to malloc, and that error vanished after the switch to GNU's
> malloc).  Maybe either cwsdpmi or DJ's malloc is buggy?

Please see if using the original cc1 stubedited to bump its stack to 
512KB (or larger, if that's not enough) makes the problem go away.  If 
so, this is a known problem with some large compiles, which could happen 
more frequently if you compile C++ programs.

Another problem might stem from using CWSDPMI that can run out of its 
heap space when an application (cc1 in this case) allocates a lot of 
memory in small chunks.  Running under another DPMI server (Windows) 
should show if that is the case here.

Btw, both of the above problems are described in the FAQ.