[lkml]   [2011]   [May]   [16]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: 答复: problem with kmemleak
On Mon, May 16, 2011 at 4:53 PM, Catalin Marinas
<> wrote:
> 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.

I am wondering why STACKTRACE doesn't select FRAME_POINTER on x86_64,
which seems necessary...

 \ /
  Last update: 2011-05-16 11:01    [W:0.058 / U:22.960 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site