All of lore.kernel.org
 help / color / mirror / Atom feed
From: Larry Finger <Larry.Finger@lwfinger.net>
To: "Frédéric Weisbecker" <fweisbec@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: How to check for memory leaks
Date: Mon, 08 Dec 2008 19:49:59 -0600	[thread overview]
Message-ID: <493DCEC7.9050203@lwfinger.net> (raw)
In-Reply-To: <c62985530812081433o5125f08gb7cad0d33a1b4104@mail.gmail.com>

Frédéric Weisbecker wrote:
> 
> You could have a look on kmemleak: http://www.procode.org/kmemleak/
> It's up to date version is on the arm development git branch (topic kmemleak):
> http://www.linux-arm.org/git?p=linux-2.6.git;a=summary
> 

I downloaded the git tree, but x86_64 architecture won't build in the kmemtest
branch. I've built an i386 kernel that I will install on a different machine.
Once I get that working, I'll try to fix the other problem and post a patch.

Larry


  parent reply	other threads:[~2008-12-09  1:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-08 22:18 How to check for memory leaks Larry Finger
2008-12-08 22:33 ` Frédéric Weisbecker
2008-12-09  1:38   ` J.R. Mauro
2008-12-09  1:45     ` Larry Finger
2008-12-09  1:49   ` Larry Finger [this message]
2008-12-09  8:55 ` Hinko Kocevar

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=493DCEC7.9050203@lwfinger.net \
    --to=larry.finger@lwfinger.net \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.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.