Re: [XenPPC] [PATCH] Print backtrace on BUG

2006-09-21 Thread Segher Boessenkool
Bah, it's too early for GCC asm: +asm(mr %0, 1 : =r (sp)); \ +asm(mflr %0 : =r (lr)); \ +asm(mflr %0; bl 1f; 1: mflr %1; mtlr %0 : =r (tp), =r (pc));\ asm(bl $+4 ; mflr %0; mtlr %1

Re: [XenPPC] [PATCH] Print backtrace on BUG

2006-09-21 Thread Jimi Xenidis
hey Amos, Please see how __warn() calls backtrace. Also lets make this a full binding and call it __full_crash that way the backtrace will be labeled and useful since the first frames are dubious. -JX On Sep 20, 2006, at 11:41 PM, Amos Waterland wrote: This makes Xen/PPC dump a backtrace

Re: [XenPPC] [PATCH] Print backtrace on BUG

2006-09-21 Thread Jimi Xenidis
hmm, this brings up an interesting issues. We curently do not print a regdump or backtrace is gdb is enabled, this is the reason why this patch exists. We obviously do not want this noise with gdb because breakpoint will become seriously annoying and may even prohibit gdb from even working

[XenPPC] [PATCH] Print backtrace on BUG

2006-09-20 Thread Amos Waterland
This makes Xen/PPC dump a backtrace when a BUG() is triggered. Signed-off-by: Amos Waterland [EMAIL PROTECTED] --- config.h | 10 +- 1 file changed, 9 insertions(+), 1 deletion(-) diff -r 5418062d2da8 xen/include/asm-powerpc/powerpc64/config.h ---