All of lore.kernel.org
 help / color / mirror / Atom feed
From: daniel.baluta@gmail.com (Daniel Baluta)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Running kmemleak without sysfs support
Date: Thu, 20 Jan 2011 14:33:36 +0200	[thread overview]
Message-ID: <AANLkTi=mEiha0rBOrX05xR=Ry5-otsB9faC29RZK7K4a@mail.gmail.com> (raw)
In-Reply-To: <1295520732.28273.4.camel@e102109-lin.cambridge.arm.com>

On Thu, Jan 20, 2011 at 12:52 PM, Catalin Marinas
<catalin.marinas@arm.com> wrote:
> On Thu, 2011-01-20 at 10:41 +0000, Daniel Baluta wrote:
>> Can I make any use of kmemcheck if I don't have sysfs
>> kernel support enabled?
>
> Kmemleak can scan output the memory and report the number of leaked
> objects but if you need to get additional information about the leaked
> objects (like backtrace), you need debugfs enabled.

How is this reporting done?  It will appear in dmesg output?

> DEBUG_FS doesn't seem to be dependent on SYSFS but I never tried to
> enable one without the other (you might be able to mount the DEBUG_FS
> somewhere other than /sys/kernel/debug/).

I see. I was using 2.6.32 where it seems that debugfs depended on sysfs.
Decoupling was done some time later [1].

thanks,
Daniel.

[1] http://kerneltrap.org/mailarchive/linux-kernel/2010/8/5/4603446

  reply	other threads:[~2011-01-20 12:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-20 10:41 Running kmemleak without sysfs support Daniel Baluta
2011-01-20 10:43 ` Daniel Baluta
2011-01-20 10:52 ` Catalin Marinas
2011-01-20 12:33   ` Daniel Baluta [this message]
2011-01-20 12:45     ` Catalin Marinas
2011-01-20 15:56 ` Greg KH
2011-01-21  9:26   ` Daniel Baluta
2011-01-21 14:02     ` Greg KH

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='AANLkTi=mEiha0rBOrX05xR=Ry5-otsB9faC29RZK7K4a@mail.gmail.com' \
    --to=daniel.baluta@gmail.com \
    --cc=kernelnewbies@lists.kernelnewbies.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.