lkml.org 
[lkml]   [2008]   [Apr]   [29]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [2/2] vmallocinfo: Add caller information

* Christoph Lameter <clameter@sgi.com> wrote:

> On Mon, 28 Apr 2008, Arjan van de Ven wrote:
>
> > > Hmmm... Why do we have CONFIG_FRAMEPOINTER then?
> >
> > to make the backtraces more accurate.
>
> Well so we display out of whack backtraces? There are also issues on
> platforms that do not have a stack in the classic sense (rotating
> register file on IA64 and Sparc64 f.e.). Determining a backtrace can
> be very expensive.

they have to solve that for kernel oopses and for lockdep somehow
anyway. Other users of stacktrace are: fault injection, kmemcheck,
latencytop, ftrace. All new debugging and instrumentation code uses it,
and for a good reason.

Ingo


\
 
 \ /
  Last update: 2008-04-29 21:35    [W:0.074 / U:0.244 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site