From: Adam Litke <agl@us.ibm.com>
To: mbligh@aracnet.com
Cc: linux-kernel@vger.kernel.org, lse-tech@lists.sourceforge.net
Subject: [RFC] Smarter stack traces using the frame pointer
Date: 04 Nov 2003 14:13:49 -0800 [thread overview]
Message-ID: <1067984031.544.23.camel@agtpad> (raw)
I was working on this for the mjb tree but I thought I'd throw it out
here in case anyone else finds it interesting. This simple change to
the stack trace code uses the frame pointer to do the trace instead of
assuming any kernel address on the stack is a return address. It makes
for much more readable stack traces.
diff -purN linux-2.6.0-test9-virgin/arch/i386/kernel/traps.c linux-2.6.0-test9-stack/arch/i386/kernel/traps.c
--- linux-2.6.0-test9-virgin/arch/i386/kernel/traps.c 2003-11-03 10:34:18.000000000 -0800
+++ linux-2.6.0-test9-stack/arch/i386/kernel/traps.c 2003-11-04 13:51:20.000000000 -0800
@@ -93,17 +93,36 @@ asmlinkage void machine_check(void);
static int kstack_depth_to_print = 24;
-void show_trace(struct task_struct *task, unsigned long * stack)
+#ifdef CONFIG_FRAME_POINTER
+void show_trace_fp(struct task_struct *task)
+{
+ unsigned long addr, ebp;
+
+ if (task == current) {
+ /* Grab ebp right from our regs */
+ asm ("movl %%ebp, %0" : "=r" (ebp) : );
+ } else {
+ /* ebp is the last reg pushed by switch_to */
+ ebp = *(unsigned long *) task->thread.esp;
+ }
+
+ while (ebp) {
+ addr = *(unsigned long *) (ebp + 4);
+ if (!kernel_text_address(addr))
+ return;
+ printk(" [<%08lx>] ", addr);
+ print_symbol("%s\n", addr);
+ ebp = *(unsigned long *) ebp;
+ }
+}
+#else
+void show_trace_guess(unsigned long * stack)
{
unsigned long addr;
if (!stack)
stack = (unsigned long*)&stack;
- printk("Call Trace:");
-#ifdef CONFIG_KALLSYMS
- printk("\n");
-#endif
while (!kstack_end(stack)) {
addr = *stack++;
if (kernel_text_address(addr)) {
@@ -111,6 +130,20 @@ void show_trace(struct task_struct *task
print_symbol("%s\n", addr);
}
}
+}
+#endif
+
+void show_trace(struct task_struct *task, unsigned long * stack)
+{
+ printk("Call Trace:");
+#ifdef CONFIG_KALLSYMS
+ printk("\n");
+#endif
+#ifdef CONFIG_FRAME_POINTER
+ show_trace_fp(task);
+#else
+ show_trace_guess(stack);
+#endif
printk("\n");
}
--
Adam Litke (agl at us.ibm.com)
IBM Linux Technology Center
(503) 578 - 3283 t/l 775 - 3283
next reply other threads:[~2003-11-04 22:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-04 22:13 Adam Litke [this message]
2003-11-05 2:21 ` [RFC] Smarter stack traces using the frame pointer Stephen Rothwell
2003-11-05 19:56 ` Martin J. Bligh
2003-11-06 11:51 ` Stephen Rothwell
2003-11-06 15:21 ` Martin J. Bligh
2003-11-10 17:46 ` Adam Litke
-- strict thread matches above, loose matches on Subject: below --
2003-11-06 20:08 Dan Kegel
[not found] <OhH5.6Y2.13@gated-at.bofh.it>
[not found] ` <QouH.36G.7@gated-at.bofh.it>
2003-11-10 18:06 ` Andi Kleen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1067984031.544.23.camel@agtpad \
--to=agl@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lse-tech@lists.sourceforge.net \
--cc=mbligh@aracnet.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox