Re: [Xen-devel] [PATCH][XEN] __trap_to_gdb should return something different

[Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>]

On 25/9/06 14:27, "Jimi Xenidis" <jimix@xxxxxxxxxxxxxx> wrote:

> 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.

How would your behaviour differ if gdbstub actually ran and eventually
returned control to you, versus the trap into the debugger being a simple
no-op? Surely the caller doesn't really care either way?

 -- Keir



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