From: Catalin Marinas <catalin.marinas@arm.com>
To: ttlxzz ccc <boyzccc@gmail.com>
Cc: "Américo Wang" <xiyou.wangcong@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: 答复: problem with kmemleak
Date: Mon, 16 May 2011 09:53:36 +0100 [thread overview]
Message-ID: <1305536016.19230.3.camel@e102109-lin.cambridge.arm.com> (raw)
In-Reply-To: <BANLkTinv6aSQMgh9ce1xaQ14_aHDPvFTxw@mail.gmail.com>
On Mon, 2011-05-16 at 08:18 +0100, ttlxzz ccc wrote:
> I'm very glad to find the reason of this problem. It's just because
> the CONFIG_FRAME_POINTER is not set :).
>
> And in dump_stack() which is defined in arch/x86/kernel/dumpstack.c,
> CONFIG_FRAME_POINTER control whether to get the bp.
>
> Now I enable CONFIG_FRAME_POINTER and I can see the full backtrace. :)
It's good you found it. I thought STACKTRACE on x86_64 would set the
necessary options like FRAME_POINTER so that it works properly. Kmemleak
only sets STACKTRACE.
--
Catalin
next prev parent reply other threads:[~2011-05-16 8:53 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 [this message]
2011-05-16 8:58 ` Américo Wang
2011-05-12 10:04 ` ttlxzz ccc
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=1305536016.19230.3.camel@e102109-lin.cambridge.arm.com \
--to=catalin.marinas@arm.com \
--cc=boyzccc@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=xiyou.wangcong@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