lkml.org 
[lkml]   [2009]   [May]   [16]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
SubjectRe: 2.6.30-rc kills my box hard - and lockdep chains
From
2009/5/17 Andrew Morton <akpm@linux-foundation.org>:
> It is a deep stack trace.
>
> And unfortunately
>
> a) that diagnostic didn't print the stack pointer value, from which
>   we can often work out if we're looking at a stack overflow.
>
> b) I regularly think it would be useful if that stack backtrace were
>   to print out the actual stack address, so we could see how much
>   stack each function is using.

I have the same sense, because lockdep uses many recursion function ,which
may cause stack overflow easily.

>
>   I just went in to hack these things up, but the x86 stacktrace
>   code which I used to understand has become stupidly complex so I
>   gave up.
>
> What tools do we have to diagnose a possible kernel stack overflow?
> There's CONFIG_DEBUG_STACK_USAGE but that's unlikely to be much use.

--
Lei Ming
--
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/

\
 
 \ /
  Last update: 2009-05-17 03:51    [from the cache]
©2003-2011 Jasper Spaans