Date: Fri, 26 Mar 1999 04:25:25 -0500
Message-Id: <199903260925.EAA23243@mescaline.gnu.org>
From: Eli Zaretskii <eliz AT gnu DOT org>
To: djgpp AT delorie DOT com
In-reply-to: <36FA5BBE.55CED66C@lmco.com> (peter.chui@lmco.com)
Subject: Re: Can't find libgcc2.c
References:  <36FA5BBE DOT 55CED66C AT lmco DOT com>
Reply-To: djgpp AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


   "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"

This is a telltale sign of code that corrupts the malloc's internal
chain of memory by overwriting the allocated memory.  Please see
section 12.2 of the DJGPP FAQ list (v2/faq211b.zip) for more details.