X-Authentication-Warning: delorie.com: mailnull set sender to djgpp-workers-bounces using -f
From: sandmann AT clio DOT rice DOT edu (Charles Sandmann)
Message-Id: <10203021522.AA15526@clio.rice.edu>
Subject: Re: Malloc/free DJGPP code
To: djgpp-workers AT delorie DOT com
Date: Sat, 2 Mar 2002 09:22:13 -0600 (CST)
In-Reply-To: <2593-Sat02Mar2002102336+0200-eliz@is.elta.co.il> from "Eli Zaretskii" at Mar 02, 2002 10:23:36 AM
X-Mailer: ELM [version 2.5 PL2]
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
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

> > Date: Fri, 01 Mar 2002 16:26:35 -0500
> > From: CBFalconer <cbfalconer AT yahoo DOT com>
> > 
> > The point of the
> > SIGSEGV would be that the rest of the system would provide a
> > traceback, while a message to stderr would not.
> 
> That's why I suggested SIGABRT instead: it also produces a traceback.

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.  Only a few dozen 
people really understand our register dump and trace stuff and why it's
our gift to them :-)