lkml.org 
[lkml]   [2011]   [May]   [13]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: 答复: problem with kmemleak
From
Date
On Fri, 2011-05-13 at 10:32 +0100, ttlxzz ccc wrote:
> I have tested kmemleak on the x86 and x86_64 architecture again. There
> is only
> 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
>
> But in the x86, there is full backtrace.

Can you enable CONFIG_BACKTRACE_SELF_TEST and check whether the
boot-time backtrace test goes ok?

--
Catalin




\
 
 \ /
  Last update: 2011-05-13 16:11    [from the cache]
©2003-2011 Jasper Spaans