Version 5.6.1 -- 11/24/2020

The debug memory allocation or "dmalloc" library has been designed as a drop in replacement for the system's malloc, realloc, calloc, free and other memory management routines while providing powerful debugging facilities configurable at runtime. These facilities include such things as memory-leak tracking, fence-post write detection, file/line number reporting, and general logging of statistics.

The library is reasonably portable having been run successfully on at least the following operating systems: AIX, DGUX, Free/Net/OpenBSD, GNU/Hurd, HPUX, Irix, Linux, OSX, NeXT, OSF/DUX, SCO, Solaris, Sunos, Ultrix, Unixware, MS Windows, and Unicos on a Cray T3E. It also provides support for the debugging of threaded programs.

The package includes the library, configuration scripts, debug utility application, test program, and documentation. Online documentation as well as the full source is available at the dmalloc home page. Details on the library's mailing list are available there as well.

Enjoy, Gray Watson

See the INSTALL file for building, installation, and quick-start notes.

Examine the dmalloc.html file which contains the user-documentation for the dmalloc subsystem. The source of all documation is the dmalloc.texi texinfo file which also can generate PDF hardcopy output with the help of the texinfo.tex file. You can download the full documentation package or read it online from the repository.

My argv library should have been included with this package (argv.[ch], argv_loc.h). I use it with all my binaries. It functions similar to the getopt routines in that it provides a standardized way of processing arguments. However, that is where the similarity ends. You have to write no C code to do the actual processing, it handles short -l and long --logfile style options, gives standard short and long usage messages, and many other features while trying to comply with POSIX specs.

The newest versions of the argv library are available online.

The initial idea of this library came from Doug Balog. He and many other net folk contributed to the design, development, and overall library and my thanks goes out to them all.

If you have any questions, comments, or problems, please use github issues to submit a question.

Gray Watson