If a bug crashes Xen then the printed backtrace is almost always sufficient.
Kdump can also be useful if we want to post-mortem analyse the heap. For
more subtle bugs, we almost always look to find a workload that reliably
repros the issue, and then we add custom tracing to Xen to narrow down the
possibilities. This latter kind of bug is not really amenable to debugging
with a traditional debugger.
-- Keir
On 14/7/07 19:41, "Kaushik Barde" <Kaushik_Barde@xxxxxxxxxxx> wrote:
> Tim,
>
> Did you get any response?
>
> -Kaushik
>
>
> -----Original Message-----
> From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
> [mailto:xen-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Tim Barbour
> Sent: Friday, June 29, 2007 11:51 AM
> To: Keir Fraser
> Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
> Subject: Re: [Xen-devel] gdbserver-xen frustration on x86_64
>
> Keir Fraser writes:
>> I'm afraid the simple answer is that gdbserver-xen spends a lot of
> the time
>> broken in one way or another because none of the core developers use
> it or
>> test it.
>
> So what debugger do the core developers use or how do they debug things
> ?
>
> Tim
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel