Messages in this thread | | | Date | Tue, 29 Apr 2008 21:29:13 +0200 | From | Ingo Molnar <> | Subject | Re: [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
| |