Date:	Wed, 12 Jan 2000 15:45:24 +0200 (IST)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender:	eliz AT is
To:	jazir <entropic AT mpx DOT com DOT au>
cc:	djgpp AT delorie DOT com
Subject:	Re: upgrade chaos
In-Reply-To:	<387C3BB5.A52F776C@mpx.com.au>
Message-ID:	<Pine.SUN.3.91.1000112154156.258A-100000@is>
MIME-Version:	1.0
Reply-To:	djgpp AT delorie DOT com
Errors-To:	dj-admin AT delorie DOT com
X-Mailing-List:	djgpp AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On Wed, 12 Jan 2000, jazir wrote:

>   i'm willing to accept that my code is buggy, so i'll do
> my best at finding it.  however, it was v2.02 that i upgraded
> from.

Then it is a little bit less evident, but I cannot really tell without 
seeing the full crash message.  Can you post it?

> As far as i could tell from the Knowledge Base, there were
> no changes to malloc or free from 2.02->2.03.

There was one small change, but it should have nothing to do with your 
situation.

> Straight after this, i tried to build it again and everything went
> smoothly.  I've been unable to reconstruct the bug.

This usually means a hardware problem.  GCC is a memory hog: it uses lots 
of RAM, and it shuffles large buffers to and fro.  It is not uncommon for 
it to be the first application that crashes when something is wrong with 
memory or CPU cache setup.

- Raw text -