### Question 18.2

How can I track down these pesky malloc problems?

A number of debugging packages exist to help track down `malloc` problems; one popular one is Conor P. Cahill's ``dbmalloc,'' posted to comp.sources.misc in 1992, volume 32. Others are ``leak,'' available in volume 27 of the comp.sources.unix archives; JMalloc.c and JMalloc.h in the ``Snippets'' collection; and MEMDEBUG from ftp.crpht.lu in pub/sources/memdebug . See also question 18.16.

A number of commercial debugging tools exist, and can be invaluable in tracking down `malloc`-related and other stubborn problems:

- Bounds-Checker for DOS, from Nu-Mega Technologies, P.O. Box 7780, Nashua, NH 03060-7780, USA, 603-889-2386.
- CodeCenter (formerly Saber-C) from Centerline Software (formerly Saber), 10 Fawcett Street, Cambridge, MA 02138-1110, USA, 617-498-3000.
- Insight, from ParaSoft Corporation, 2500 E. Foothill Blvd., Pasadena, CA 91107, USA, 818-792-9941, insight@parasoft.com .
- Purify, from Pure Software, 1309 S. Mary Ave., Sunnyvale, CA 94087, USA, 800-224-7873, info-home@pure.com .
- SENTINEL, from AIB Software, 46030 Manekin Plaza, Dulles, VA 20166, USA, 703-430-9247, 800-296-3000, info@aib.com .

Read sequentially: prev next up top

This page by Steve Summit // Copyright 1995 // mail feedback