From: Kevin Buettner <kev@primenet•com>
To: mnorton@cisco•com, linuxppc-dev@lists•linuxppc.org
Subject: Re: Purify or Comparable???
Date: Wed, 4 Oct 2000 10:14:07 -0700 [thread overview]
Message-ID: <1001004171407.ZM31953@saguaro.lan> (raw)
In-Reply-To: Michael Norton <mnorton@cisco.com> "Purify or Comparable???" (Oct 4, 5:44am)
On Oct 4, 5:44am, Michael Norton wrote:
> What software tool is recommended for examining memory leaks in code?
> Does a close cousin of Purify exist for LinuxPPC/ What do you coders
> recommend?
I've never used Purify, so I can't offer a comparison, but...
I've found that dmalloc works quite well for debugging memory
allocation related problems. See http://dmalloc.com/.
Kevin
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-10-04 17:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-04 9:44 Purify or Comparable??? Michael Norton
2000-10-04 17:14 ` Kevin Buettner [this message]
2000-10-04 18:10 ` Erik Winkler
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1001004171407.ZM31953@saguaro.lan \
--to=kev@primenet$(echo .)com \
--cc=linuxppc-dev@lists$(echo .)linuxppc.org \
--cc=mnorton@cisco$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox