|To:||Atsushi Nemoto <email@example.com>|
|Subject:||Re: [PATCH] dump_stack() based on prologue code analysis|
|From:||David Daney <firstname.lastname@example.org>|
|Date:||Thu, 27 Jul 2006 09:54:58 -0700|
|User-agent:||Mozilla Thunderbird 1.0.7-1.1.fc3 (X11/20050929)|
Atsushi Nemoto wrote:
Instead of dump all possible address in the stack, unwind the stack frame based on prologue code analysis, as like as get_chan() does. While the code analysis might fail for some reason, there is a new kernel option "raw_show_trace" to disable this feature. Signed-off-by: Atsushi Nemoto <email@example.com>
Let me start by saying I have not analyzed how all this code works, but I have done something similar in user space.
Since the kernel ABI does not use gp, many functions may not have a prolog (especially when compiled with newer versions of GCC). In the user space case, most leaf functions have no prolog. For the kernel I would imagine that many non-leaf functions (simple non-leaf functions that do only a tail call) would also not have a prolog.
I would be worried that many stack traces would become less useful.If this were conditional on -fno-omit-frame-pointer, then I think it would be a good idea.
|<Prev in Thread]||Current Thread||[Next in Thread>|
|Previous by Date:||is sde lite a complete toolchain?, Shan Wang|
|Next by Date:||Re: [PATCH] dump_stack() based on prologue code analysis, Thiemo Seufer|
|Previous by Thread:||Re: [PATCH] dump_stack() based on prologue code analysis, Atsushi Nemoto|
|Next by Thread:||Re: [PATCH] dump_stack() based on prologue code analysis, Thiemo Seufer|
|Indexes:||[Date] [Thread] [Top] [All Lists]|