Safer malloc/free

[cliff click]

To help my debugging I wrote some routines for doing "safer" malloc & free.
They do some minor checks for over/under running a malloc'd block of memory,
and make sure I free all my blocks exactly once.  Does anyone else have such
"safety" wrappers for basic system utilities (closing all open files, etc)
to help debugging?

Please e-mail, and I will summerize (sic).

-- 
Cliff Click, Software Contractor at Large
Business: uunet.uu.net!ficc!cliff, cliff at ficc.uu.net, +1 713 274 5368 (w).
Disclaimer: lost in the vortices of nilspace...       +1 713 568 3460 (h).