Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!uwm.edu!zaphod.mps.ohio-state.edu!sol.ctr.columbia.edu!cica!iuvax!purdue!haven!h.cs.wvu.wvnet.edu!cerc.wvu.wvnet.edu!babcock.cerc.wvu.wvnet.edu
From: lss@babcock.cerc.wvu.wvnet.edu (Linda S. Saus)
Newsgroups: comp.lang.c
Subject: Re: Request - malloc/free wrappers to aid debugging
Message-ID: <354@cerc.wvu.wvnet.edu.edu>
Date: 22 Jan 90 14:30:53 GMT
References: <gZhzPmi00WB8N9WoYF@andrew.cmu.edu>
Sender: news@cerc.wvu.wvnet.edu
Lines: 22

From article <gZhzPmi00WB8N9WoYF@andrew.cmu.edu>, by dg3s+@andrew.cmu.edu (David Gentzel):
> I vaugely recall reading a message (or messages) on this list some time ago
> about a set of wrapper functions/macros for malloc/free to aid debugging.
> They (if my memory serves) kept track of malloced/freed memory and allowed
> you to detect such common snafus as multiple frees and memory leaks.
> 
On SUN systems, the following is available:  See man pages for free to
get complete details.

DIAGNOSTICS
     More detailed diagnostics can be made available to  programs
     using  malloc, calloc, realloc, valloc, memalign, cfree, and
     free, by including a special relocatable object file at link
     time  (see FILES). This file also provides routines for con-
     trol of error handling  and  diagnosis,  as  defined  below.
     Note:  these  routines  are  not  defined  in  the  standard
     library.
             
FILES
     /usr/lib/debug/malloc.o  diagnostic  versions  of   malloc()
                              routines.