From: "Neil J. Fergusson" <fergusson@ca.metsci.com>
To: kplug-newbie@kernel-panic.org
Cc: kplug-lpsg@kernel-panic.org,
mehul radheshyam choube <mehulchoube_lpsg@rediffmail.com>,
linux-mm@kvack.org, plug-mail@codio.net, plug-mail@plug.org.in
Subject: Re: memory leakage detection tools
Date: Fri, 25 Jan 2002 11:34:01 -0800 [thread overview]
Message-ID: <3C51B329.5080409@ca.metsci.com> (raw)
In-Reply-To: <Pine.GSU.4.30_heb2.09.0201191805440.24506-100000@actcom.co.il>
Try "Bounds Checking", a GPL-ed (I believe) program.
- Neil Fergusson
guy keren wrote:
> On 19 Jan 2002, mehul radheshyam choube wrote:
>
>
>> i am writing c program which uses lot of pointer variables.
>>
> [...snip...]
>
>> but now i want to check whether there is any memory leakage.can
>> anybody suggest me any free tool for this.
>>
>
> i've conducted some "research" (you might call it) for development tools
> for linux (including malloc debugging libraries) for a lecture i carried
> in our local linux club - look at the slides:
> http://linuxclub.il.eu.org/newcomers/lectures/6/ide.html
>
> and specifically under 'Debug libraries'.
>
> hope this helps,
> --
> guy
>
> "For world domination - press 1,
> or dial 0, and please hold, for the creator." -- nob o. dy
>
--
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/
next prev parent reply other threads:[~2002-01-25 19:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-19 10:39 mehul radheshyam choube
2002-01-19 16:11 ` guy keren
2002-01-25 19:34 ` Neil J. Fergusson [this message]
2002-01-25 19:50 Koni
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=3C51B329.5080409@ca.metsci.com \
--to=fergusson@ca.metsci.com \
--cc=kplug-lpsg@kernel-panic.org \
--cc=kplug-newbie@kernel-panic.org \
--cc=linux-mm@kvack.org \
--cc=mehulchoube_lpsg@rediffmail.com \
--cc=plug-mail@codio.net \
--cc=plug-mail@plug.org.in \
/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