| |
|
 |
|
 |
|
|
|
| |
|
|
xen-ppc-devel
Re: [Xen-devel] [PATCH][XEN] __trap_to_gdb should return something diffe
On Sep 23, 2006, at 1:18 PM, Keir Fraser wrote:
On 22/9/06 4:07 pm, "Jimi Xenidis" <jimix@xxxxxxxxxxxxxx> wrote:
--text follows this line--
This patch allows the caller to find out if the gdbstub actually did
anything.
Signed-off-by: Jimi Xenidis <jimix@xxxxxxxxxxxxxx>
What different actions do you envisage the caller will take? If
they are
reasonable, perhaps they should be explicitly specified in a return-
code
enumeration?
Currently there are two failure cases:
1) GDB had no transport available for its use (UART or otherwise)
2) "unexpected trap", usually another trap occurs while gdb is in
control
I suppose we could have (1) -EIO and (2) -EBUSY.
My logic was that either gdb was available or not and that I needed
to continue as if gdb was not enabled at all.
-JX
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
|
|
| |
|
Home