Prev: [PATCH] x86/pci: exclude mrst pci code for other platform
Next: markup_oops.pl and GDB: Let GDB can handle kernel oops stack message
From: Steven J. Magnani on 24 Feb 2010 16:10
Adjust the pointer used as the start of a stack dump so that the dump
begins with the caller of dump_stack(). This makes the dump easier to
interpret.

Signed-off-by: Steven J. Magnani <steve(a)digidescorp.com>
---
diff -uprN a/arch/microblaze/kernel/traps.c b/arch/microblaze/kernel/traps.c
--- a/arch/microblaze/kernel/traps.c 2010-02-24 14:12:01.000000000 -0600
+++ b/arch/microblaze/kernel/traps.c 2010-02-24 14:56:21.000000000 -0600
@@ -73,8 +73,10 @@ void show_stack(struct task_struct *task
if (task)
sp = (unsigned long *) ((struct thread_info *)
(task->stack))->cpu_context.r1;
- else
+ else {
sp = (unsigned long *)&sp;
+ sp -= 2; /* Pick up caller of dump_stack() */
+ }
}

stack = sp;

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
 | 
Pages: 1
Prev: [PATCH] x86/pci: exclude mrst pci code for other platform
Next: markup_oops.pl and GDB: Let GDB can handle kernel oops stack message