From: Erik Winkler <ewinkler@erols.com>
To: Kevin Buettner <kev@primenet.com>
Cc: mnorton@cisco.com, linuxppc-dev@lists.linuxppc.org
Subject: Re: Purify or Comparable???
Date: Wed, 04 Oct 2000 14:10:27 -0400 [thread overview]
Message-ID: <39DB7292.3795DC65@erols.com> (raw)
In-Reply-To: 1001004171407.ZM31953@saguaro.lan
I've used purify in a SunOS environment and it worked great. Combined with
Pure Coverage I was able to test all my code for memory leaks. I'm not
sure if it's available for LinuxPPC, but maybe for Linux i386.
Erik
Kevin Buettner wrote:
> 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/
prev parent reply other threads:[~2000-10-04 18:10 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
2000-10-04 18:10 ` Erik Winkler [this message]
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=39DB7292.3795DC65@erols.com \
--to=ewinkler@erols.com \
--cc=kev@primenet.com \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=mnorton@cisco.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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;
as well as URLs for NNTP newsgroup(s).