[XenPPC] Re: [Xen-devel] [Patch] [RFC] avoid debugger_trap when we don't expect

Hi, Keir >On 30/1/08 08:48, "Akio Takebe" <[EMAIL PROTECTED]> wrote: > >>> This doesn't need to be fixed on x86 -- the int3 handler will return >>> silently if the debugger is not configured. It would be nice if the ia64 >>> handler would do the same. If that is not possible then change only ia64

[XenPPC] Re: [Xen-devel] [Patch] [RFC] avoid debugger_trap when we don't expect

On 30/1/08 08:48, "Akio Takebe" <[EMAIL PROTECTED]> wrote: >> This doesn't need to be fixed on x86 -- the int3 handler will return >> silently if the debugger is not configured. It would be nice if the ia64 >> handler would do the same. If that is not possible then change only ia64 >> code and if

[XenPPC] Re: [Xen-devel] [Patch] [RFC] avoid debugger_trap when we don't expect

Hi, Keir >This doesn't need to be fixed on x86 -- the int3 handler will return >silently if the debugger is not configured. It would be nice if the ia64 >handler would do the same. If that is not possible then change only ia64 >code and if you need to be able to probe gdbstub configuration then ad

[XenPPC] Re: [Xen-devel] [Patch] [RFC] avoid debugger_trap when we don't expect

This doesn't need to be fixed on x86 -- the int3 handler will return silently if the debugger is not configured. It would be nice if the ia64 handler would do the same. If that is not possible then change only ia64 code and if you need to be able to probe gdbstub configuration then add a public fun