Message-ID:	<3E713255.B2A42BDB@yahoo.com>
Date:	Thu, 13 Mar 2003 20:37:25 -0500
From:	CBFalconer <cbfalconer AT yahoo DOT com>
Organization:	Ched Research
X-Mailer:	Mozilla 4.75 [en] (Win98; U)
X-Accept-Language:	en
MIME-Version:	1.0
To:	djgpp-workers <djgpp-workers AT delorie DOT com>
Subject:	nmalloc revisited
Reply-To:	cbfalconer AT worldnet DOT att DOT net

I have just noticed a C99 restriction against raising signals
within the library.  nmalloc does raise SIGABRT in several cases,
where the memory arena has become fouled.  This is concentrated in
the routine badcallabort(), which is called from various places.

Is this worth worrying about, given that any such fouled arena
must result from some earlier error, which leads to undefined
behaviour.  My philosophy was that once the arena cannot be
trusted, it would be foolish to allow the application to continue.

BTW the nmalloc.c code has not been altered since June 2002, and
the overall package is unaltered since November 2002 (some
documentation changes and testing).  It remains available at:

  <http://cbfalconer.home.att.net/download/nmalloc.zip>

-- 
Chuck F (cbfalconer AT yahoo DOT com) (cbfalconer AT worldnet DOT att DOT net)
   Available for consulting/temporary embedded and systems.
   <http://cbfalconer.home.att.net>  USE worldnet address!

- Raw text -