X-Authentication-Warning: delorie.com: mailnull set sender to djgpp-workers-bounces using -f
Date: Sat, 02 Mar 2002 20:06:11 +0200
From: "Eli Zaretskii" <eliz AT is DOT elta DOT co DOT il>
Sender: halo1 AT zahav DOT net DOT il
To: djgpp-workers AT delorie DOT com
Message-Id: <2593-Sat02Mar2002200610+0200-eliz@is.elta.co.il>
X-Mailer: emacs 21.2.50 (via feedmail 8 I) and Blat ver 1.8.9
In-reply-to: <10203021522.AA15526@clio.rice.edu> (sandmann@clio.rice.edu)
Subject: Re: Malloc/free DJGPP code
References:  <10203021522 DOT AA15526 AT clio DOT rice DOT edu>
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

> From: sandmann AT clio DOT rice DOT edu (Charles Sandmann)
> Date: Sat, 2 Mar 2002 09:22:13 -0600 (CST)
> 
> SIGABRT is fine, but I'd also like to see a message why the abort
> happened, something like:
> 
> Malloc memory control structures are corrupt, probably due to program
> writing data beyond the end of the allocated data.
> 
> or
> 
> Attempt to free a memory block not allocated with malloc.
> 
> Real exceptions happen because we didn't catch them - so we show everything
> we know about it.  If we are going to raise an exception, lets tell the
> user why, instead of making it hard to understand.

Yes, I agree (although the crash message printed for SIGABRT does say
``raised at 0xNNNNN'', with EIP from the place where you call `raise').