Mail Archives: djgpp/1999/06/07/13:04:14
I have uploaded version 0.30 of YAMD, Yet Another Malloc Debugger, to:
http://www.cartsys.com/eldredge/n/yamd/
This fixes problems several people were reporting with interactions
between YAMD and libc. There are probably other bugfixes which I've
forgotten. If you had any problems with previous versions, please try
this one.
One major user-visible change has been made: It is no longer possible to
disable YAMD at runtime. This is a side-effect of the above changes
which can't cleanly be avoided. On the flip side, you no longer have to
set YAMD_ENABLE.
What is YAMD?
===================================================================
YAMD is a package for finding bugs related to dynamic memory allocation
(pointer overruns, memory leaks, etc). Among its special features:
* Paging mechanisms are used to trap illegal memory accesses. This
means that reads as well as writes can be caught, and are caught
immediately, rather than at some later time.
* All operations are logged with a traceback to aid in finding why some
allocation or other went awry.
* No changes to your source are required to use YAMD.
* Everything else you'd expect from a malloc debugger; checking of
"obvious" errors like multiple freeing, etc.
YAMD also works under Linux, and in fact supports some additional
features there.
Some restrictions do apply:
- Several DPMI 1.0 features are essential to the way YAMD works;
therefore, **it will only work under plain DOS with CWSDPMI as the DPMI
server**.
- A fairly large amount of swap space is recommended.
Copying policy is GPL.
Please check it out, and report any successes/failures/bugs to me:
<nate AT cartsys DOT com>.
=======================================================================
--
Nate Eldredge
nate AT cartsys DOT com
- Raw text -