I know that in the UX area there are tools to help find leaks in code.
We once used one to check path flow analysis, and a side benefit was
malloc/free pair checking, IIRC. This involved a pre-processor pass over the
code that inserted code at each conditional branch, and at run time this
code logged the path taken to a file. At the end of the testing you could
summarize the logs to show what % of all the possible paths had been
exercised. Along the way it could also trap Mallocs and Frees and log them
for analysis. The only unfreed areas would be those that held global data
that lived for the whole run.
HTH
jp
----- Original Message -----
From: ":-) Craig Lalley" <[log in to unmask]>
To: <[log in to unmask]>
Sent: Thursday, February 20, 2003 5:53 AM
Subject: [HP3000-L] Debug and Memory leaks


> Here's a tough one.
>
> I am suspecting a program of having a memory leak.  How do I prove it,
> other than the symptoms?
>
> Is there a way in DEBUG to determine how much memory a specific pin is
> currently using?
>
> Bonus question: when analyzing a memory dump, how do I view the command
> history of a session (process)?
>
> I know every one is busy formulating thier answers to the problems of
> the world, maybe this can help narrow the focus.  :)
>
> Regards,
>
> -Craig
>
>
> __________________________________________________
> Do you Yahoo!?
> Yahoo! Shopping - Send Flowers for Valentine's Day
> http://shopping.yahoo.com
>
> * To join/leave the list, search archives, change list settings, *
> * etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *