Just a minor new twist on free()

[Conor P. Cahill]

I know I hate people pushing thier own software, but I thought just one 
more time....

In article <9010111342.AA18267 at bisco.kodak.COM> nobody at Kodak.COM writes:
>  Wouldn't it be more graceful to check for invalid data (such as, but not
>  limited to NULL pointers), and on an error condition print a MESSAGE and
>  exit gracefully (perhaps with a core dump to allow a debugger to give you
>  trace-back information). 

This is exactly how the debuggin malloc library that was posted to c.s.u
back in may works.  You link it with your program (no changes are necessary
to your program, you don't even have to re-compile it - just relink it)
and you have a full set of checks on the typical problems that are 
prevalent in malloc usage.

Try it, you'll like it.
-- 
Conor P. Cahill            (703)430-9247        Virtual Technologies, Inc.,
uunet!virtech!cpcahil                           46030 Manekin Plaza, Suite 160
                                                Sterling, VA 22170