From: Dan Kegel <dank@kegel.com>
To: mss59@att.net
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Memory Profiling Tool
Date: Tue, 02 Sep 2003 13:51:23 -0700 [thread overview]
Message-ID: <3F5502CB.9030501@kegel.com> (raw)
In-Reply-To: <200309021344.IAA18035@lists.linuxppc.org>
mss59@att.net wrote:
> Is there any memory profiling and leak detection tool available which
> works for both PPC and X86??
Here's what I know about.
1. There's a utility built into glibc which may be of some help:
http://www.gnu.org/manual/glibc-2.2.5/html_node/Allocation-Debugging.html#Allocation%20Debugging
but it's a bit minimal.
2. x86 only - valgrind, of course. God's gift to x86 programmers. Shame
it's not been ported to ppc.
3. libmudflap. This is very promising; see
http://people.redhat.com/dnovillo/Papers/nordu2003-slides.pdf
http://www.linux.org.uk/~ajh/gcc/gccsummit-2003-proceedings.pdf
However, it's part of the SSA branch of gcc-3.4, so you'll need to use
something like http://kegel.com/crosstool to build it.
I am hoping to try this out on ppc sometime, but haven't yet.
FWIW, it's provided with Red Hat's taroon beta, so it must
be getting close to usable.
If you're debugging c++, you should also read
http://gcc.gnu.org/onlinedocs/libstdc++/debug.html
- Dan
--
Dan Kegel
http://www.kegel.com
http://counter.li.org/cgi-bin/runscript/display-person.cgi?user=78045
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-09-02 20:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-02 13:43 Memory Profiling Tool mss59
2003-09-02 20:51 ` Dan Kegel [this message]
2003-09-04 11:02 ` Is there any tool like purify(memory leak check tool) for Embedded Linux/ELDK environment John Zhou
2003-09-04 5:58 ` Memory Profiling Tool Der Herr Hofrat
2003-09-04 14:42 ` Dan Kegel
2003-09-05 8:26 ` display top CPU processes top tool John Zhou
2003-09-05 9:02 ` Jaap-Jan Boor
2003-09-05 9:23 ` John Zhou
2003-09-05 16:00 ` Dan Kegel
2003-09-05 16:39 ` Mark Hatle
-- strict thread matches above, loose matches on Subject: below --
2003-09-03 15:00 Memory Profiling Tool Keith Pickens
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=3F5502CB.9030501@kegel.com \
--to=dank@kegel.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=mss59@att.net \
/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.