From: Michael Norton <mnorton@cisco.com>
To: linuxppc-dev@lists.linuxppc.org
Subject: Purify or Comparable???
Date: Wed, 04 Oct 2000 05:44:34 -0400 [thread overview]
Message-ID: <39DAFC02.52938515@cisco.com> (raw)
hi,
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?
thanks,
Mike
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2000-10-04 9:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-04 9:44 Michael Norton [this message]
2000-10-04 17:14 ` Purify or Comparable??? Kevin Buettner
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=39DAFC02.52938515@cisco.com \
--to=mnorton@cisco.com \
--cc=linuxppc-dev@lists.linuxppc.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.