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
On Wed, Jan 30, 2008 at 09:41:36AM +, Keir Fraser wrote:
> A new releaase candidate is tagged in
> http://xenbits.xensource.com/xen-3.1-testing.hg. Assuming no problems are
> revealed by testing, I'd like to make this the proper 3.1.3 release asap.
I did some very basic testing of bits based
A new releaase candidate is tagged in
http://xenbits.xensource.com/xen-3.1-testing.hg. Assuming no problems are
revealed by testing, I'd like to make this the proper 3.1.3 release asap.
Thanks,
Keir
___
Xen-ppc-devel mailing list
Xen-ppc-devel@lists
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
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
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
