[XenPPC] [xenppc-unstable] [XEN] __trap_to_gdb should return something different on failure

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

# HG changeset patch
# User Jimi Xenidis <jimix@xxxxxxxxxxxxxx>
# Node ID e5b1f6154f3121ad3b4172de17f9618f1acc3e90
# Parent  e0bb62683805bc0dcd6ca5198b140f5910dbd358
[XEN] __trap_to_gdb should return something different on failure
This patch allows the caller to find out if the gdbstub actually did
anything.

Signed-off-by: Jimi Xenidis <jimix@xxxxxxxxxxxxxx>
---
 xen/common/gdbstub.c |    4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)

diff -r e0bb62683805 -r e5b1f6154f31 xen/common/gdbstub.c
--- a/xen/common/gdbstub.c      Fri Sep 22 11:02:47 2006 -0400
+++ b/xen/common/gdbstub.c      Fri Sep 22 11:08:12 2006 -0400
@@ -481,7 +481,7 @@ __trap_to_gdb(struct cpu_user_regs *regs
     if ( gdb_ctx->serhnd < 0 )
     {
         dbg_printk("Debugger not ready yet.\n");
-        return 0;
+        return -1;
     }
 
     /* We rely on our caller to ensure we're only on one processor
@@ -500,7 +500,7 @@ __trap_to_gdb(struct cpu_user_regs *regs
     {
         printk("WARNING WARNING WARNING: Avoiding recursive gdb.\n");
         atomic_inc(&gdb_ctx->running);
-        return 0;
+        return -1;
     }
 
     if ( !gdb_ctx->connected )

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