linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Koni <mhw6@cornell.edu>
To: mehul radheshyam choube <mehulchoube_lpsg@rediffmail.com>
Cc: kplug-newbie@kernel-panic.org, linux-mm@kvack.org
Subject: Re: memory leakage detection tools
Date: 25 Jan 2002 14:50:13 -0500	[thread overview]
Message-ID: <1011988214.8838.12.camel@abertzale> (raw)

You can also try "memprof" -- a gnome app I believe, for visualizing and
tracking memory leaks by using a mark-and-sweep garbage collector to
find allocated chunks that are not referenced anywhere, or something
like that. Worked very well for me on a few items. Sometimes its helpful
to link against debug builds of libraries though as I found sometimes
the stack traces would get messed up without the debugging symbols for
glibc and what not. Only problem with the memprof version I used (it was
a while ago) is I couldn't figure out how to set the command line
arguments for the process I wanted to profile.

Good luck!

Cheers,
Koni

Try "Bounds Checking", a GPL-ed (I believe) program.

 - Neil Fergusson


guy keren wrote:

[snip]

-- 
mhw6@cornell.edu
Koni (Mark Wright)
Solanaceae Genome Network	250 Emerson Hall - Cornell University
Strategic Forecasting		242 Langmuir Laboratory
Lightlink Internet		http://www.lightlink.com/

"If I'm right 90% of the time, why quibble about the other 3%?"

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/

             reply	other threads:[~2002-01-25 19:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-25 19:50 Koni [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-01-19 10:39 mehul radheshyam choube
2002-01-19 16:11 ` guy keren
2002-01-25 19:34   ` Neil J. Fergusson

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=1011988214.8838.12.camel@abertzale \
    --to=mhw6@cornell.edu \
    --cc=kplug-newbie@kernel-panic.org \
    --cc=linux-mm@kvack.org \
    --cc=mehulchoube_lpsg@rediffmail.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