[Xen-changelog] I've found it useful to display the panic message *before* dropping into the

[Xen patchbot -unstable <patchbot-unstable@xxxxxxxxxxxxxxxxxxx>]

# HG changeset patch
# User kaf24@xxxxxxxxxxxxxxxxxxxx
# Node ID e3e4c8b564e2c08871980de1aa5ea8bbaccf4d07
# Parent  5618b13ac97fa7db290922c47f46cfb431632917
I've found it useful to display the panic message *before* dropping into the 
debugger. Once there it may be very difficult to find the original message, 
and often a debugger isn't even needed if you can see what panicked.

Signed-off-by: Hollis Blanchard <hollisb@xxxxxxxxxx>

diff -r 5618b13ac97f -r e3e4c8b564e2 xen/drivers/char/console.c
--- a/xen/drivers/char/console.c        Wed Mar 15 10:06:45 2006
+++ b/xen/drivers/char/console.c        Wed Mar 15 10:07:26 2006
@@ -683,8 +683,6 @@
     (void)vsnprintf(buf, sizeof(buf), fmt, args);
     va_end(args);
 
-    debugger_trap_immediate();
-
     /* Spit out multiline message in one go. */
     spin_lock_irqsave(&lock, flags);
     printk("\n****************************************\n");
@@ -693,6 +691,8 @@
     printk("****************************************\n\n");
     printk("Reboot in five seconds...\n");
     spin_unlock_irqrestore(&lock, flags);
+
+    debugger_trap_immediate();
 
     watchdog_disable();
     mdelay(5000);

_______________________________________________
Xen-changelog mailing list
Xen-changelog@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-changelog