Sender: nate AT cartsys DOT com
Message-ID: <36FAB7CF.91D8C954@cartsys.com>
Date: Thu, 25 Mar 1999 14:25:19 -0800
From: Nate Eldredge <nate AT cartsys DOT com>
X-Mailer: Mozilla 4.08 [en] (X11; I; Linux 2.2.3 i586)
MIME-Version: 1.0
To: djgpp AT delorie DOT com
Subject: Re: Can't find libgcc2.c
References: <36FA5BBE DOT 55CED66C AT lmco DOT com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Reply-To: djgpp AT delorie DOT com

peter DOT chui AT lmco DOT com wrote:
> 
> Hello,
> 
> The program that I compiled occasionally crashes with a,
> 
> "Exiting due to signal SIGSEGV"
> "Page fault at eip=..."
> 
> message. When I used symify to get the line numbers, most of the ones
> that crash end up at,
> 
> "_malloc+99"
> "__builtin_new+44, line 0 of libgcc2.c"
> 
> I can't find a copy of libgcc2.c in any of the .zip files.

It's the file in the libgcc source where the `new' operator is
implemented.  You can get it from the gcc281s.zip package, but it's
really not interesting; all it does is call `malloc', as you can see.

Your bug is probably corrupting the heap, which makes `malloc' crash;
check for pointer overruns and such.
-- 

Nate Eldredge
nate AT cartsys DOT com