home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.lang.c
- Path: sparky!uunet!virtech!cpcahil
- From: cpcahil@vti.com (Conor P. Cahill)
- Subject: Re: Help me track down memory leakage
- Message-ID: <BxwtGr.82n@vti.com>
- Organization: Virtual Technologies Inc.
- References: <BxuLIr.DK@rice.edu>
- Date: Wed, 18 Nov 1992 11:34:02 GMT
- Lines: 25
-
- abuhr@owlnet.rice.edu (Aaron M. Buhr) writes:
-
- > I've inherited a very large C program that I am trying to maintain and
- >expand, and I've come to the point where I HAVE to find out where the
- >program's leaking memory. The program starts out with about 7MB virtual
- >mem usage, 6MB real, and grows over the course of 6-8 hours to around 20MB
- >virtual, 10MB real. The program uses straight malloc() and realloc() calls.
- >I don't know where or how to start trying to track this down. Any help
- >would be greatly appreciated. Email is preferred, but I'll try to watch
- >the posts to this group as well. Much thanks in advance.
-
- Assuming you are talking about a program in a UNIX environment, you could
- use my freeware dbmalloc (or malloclib) library which does have some support
- for tracking memory leaks. This was posted to comp.sources.misc in Sept.
-
- Another (better, but I'm biased) solution would be to use our SENTINEL
- product which you would just link in and get a full report of memory
- leaks in addition to lots of other interesting debugging capabilities.
- Send email if you would like additional information.
-
- --
- *** SENTINEL(tm) The ultimate Debugging Environment - email for more info ***
-
- Conor P. Cahill (703)430-9247 cpcahil@virtech.vti.com
- Virtual Technologies, Inc. 46030 Manekin Plaza Dulles, VA 20166
-