From: ttlxzz ccc <boyzccc@gmail.com>
To: Maxin B John <maxin.john@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: problem with kmemleak
Date: Thu, 12 May 2011 18:04:51 +0800 [thread overview]
Message-ID: <BANLkTim0OGhBV4Ut81C3twKOBBjxUnkczQ@mail.gmail.com> (raw)
In-Reply-To: <BANLkTi=S3VR1mxc0bsL4+N3ksHeo3scg3A@mail.gmail.com>
I am chenxi, too :)
On Thu, May 12, 2011 at 5:44 PM, Maxin B John <maxin.john@gmail.com> wrote:
> Hi,
>
> Could you please share some more information about your setup ?
>
> Regards,
> Maxin
>
> On Thu, May 12, 2011 at 4:13 AM, ttlxzz ccc <boyzccc@gmail.com> wrote:
>> help~~~：） please ！thx！！
>>
>> On Thu, May 12, 2011 at 10:06 AM, ttlxzz ccc <boyzccc@gmail.com> wrote:
>>> Hi, all:
>>>
>>>
>>>
>>> I just want to use kmemleak, so I make the CONFIG_DEBUG_KMEMLEAK and
>>> CONFIG_DEBUG_FS on, mount the debugfs.
>>>
>>> But when I insmod mm/kmemleak-test.ko, echo scan >
>>> /sys/kernel/debug/kmemleak and cat /sys/kernel/debug/kmemleak. I just
>>> see this:
>>>
>>> unreferenced object 0xffffc90012d21000 (size 64):
>>>
>>> comm "insmod", pid 13092, jiffies 4298369684
>>>
>>> hex dump (first 32 bytes):
>>>
>>> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
>>>
>>> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
>>>
>>> backtrace:
>>>
>>> [<ffffffffffffffff>] 0xffffffffffffffff
>>>
>>> unreferenced object 0xffffc90012d24000 (size 64):
>>>
>>> comm "insmod", pid 13092, jiffies 4298369684
>>>
>>> hex dump (first 32 bytes):
>>>
>>> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
>>>
>>> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
>>>
>>> backtrace:
>>>
>>> [<ffffffffffffffff>] 0xffffffffffffffff
>>>
>>> unreferenced object 0xffffc90012d27000 (size 64):
>>>
>>> comm "insmod", pid 13092, jiffies 4298369684
>>>
>>> hex dump (first 32 bytes):
>>>
>>> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
>>>
>>> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
>>>
>>> backtrace:
>>>
>>> [<ffffffffffffffff>] 0xffffffffffffffff
>>>
>>> There is no other backtrace except [<ffffffffffffffff>]
>>> 0xffffffffffffffff. Then I read the mm/kmemleak.c. In
>>> kmemleak_seq_show(), I find that the object->trace_len is 1.
>>>
>>>
>>>
>>> How can I get the full backtrace?
>>>
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>> Please read the FAQ at http://www.tux.org/lkml/
>>
>
next prev parent reply other threads:[~2011-05-12 10:04 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-12 2:06 problem with kmemleak ttlxzz ccc
2011-05-12 3:13 ` ttlxzz ccc
2011-05-12 9:44 ` Maxin B John
2011-05-12 9:59 ` 答复: " chenxi
2011-05-12 11:16 ` Daniel Baluta
2011-05-12 12:01 ` ttlxzz ccc
2011-05-12 14:18 ` Américo Wang
2011-05-12 14:33 ` ttlxzz ccc
2011-05-12 14:49 ` Américo Wang
2011-05-12 15:00 ` Daniel Baluta
2011-05-12 15:04 ` Catalin Marinas
2011-05-12 15:09 ` ttlxzz ccc
[not found] ` <BANLkTik6c8-g8FrXZy8-V35W6-Th++5p_A@mail.gmail.com>
2011-05-13 9:32 ` ttlxzz ccc
2011-05-13 14:08 ` Catalin Marinas
2011-05-15 6:01 ` ttlxzz ccc
2011-05-16 7:18 ` ttlxzz ccc
2011-05-16 8:53 ` Catalin Marinas
2011-05-16 8:58 ` Américo Wang
2011-05-12 10:04 ` ttlxzz ccc [this message]
2011-05-12 13:52 ` ttlxzz ccc
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=BANLkTim0OGhBV4Ut81C3twKOBBjxUnkczQ@mail.gmail.com \
--to=boyzccc@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maxin.john@gmail.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