This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] Re: follow-up to guest debug support patches

To: jfv@xxxxxxxxxxxx
Subject: Re: [Xen-devel] Re: follow-up to guest debug support patches
From: Kip Macy <kip.macy@xxxxxxxxx>
Date: Sat, 12 Mar 2005 11:05:30 -0800
Cc: Ian Pratt <m+Ian.Pratt@xxxxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxxxx, Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>, Ian.Pratt@xxxxxxxxxxxx, Christian Limpach <Christian.Limpach@xxxxxxxxxxxx>, jfv@xxxxxxxxxx
Delivery-date: Sat, 12 Mar 2005 19:07:12 +0000
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=myaUG/NPrlPyHa4ZSDtZRSJvJNSeoDgvc3kxFNuc5yCMY95a+dECoIkg9MPzc+EKaHHWsH3wnij9UHqBh8nGwaMJgKxwXNdTR99L8VdPa+E03GER32jFOqLjFzXD+fPMo+wmsrZ9lckjt2abOWySJHIggArAX//lE/oy3MvDzD4=
Envelope-to: xen+James.Bulpin@xxxxxxxxxxxx
In-reply-to: <20050312185848.GA16403@xxxxxxxxxxxxxxxxxx>
List-archive: <http://sourceforge.net/mailarchive/forum.php?forum=xen-devel>
List-help: <mailto:xen-devel-request@lists.sourceforge.net?subject=help>
List-id: List for Xen developers <xen-devel.lists.sourceforge.net>
List-post: <mailto:xen-devel@lists.sourceforge.net>
List-subscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=subscribe>
List-unsubscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=unsubscribe>
References: <A95E2296287EAD4EB592B5DEEFCE0E9D1E35F7@xxxxxxxxxxxxxxxxxxxxxxxxxxx> <b1fa29170503121040171af6ce@xxxxxxxxxxxxxx> <20050312185848.GA16403@xxxxxxxxxxxxxxxxxx>
Reply-to: Kip Macy <kip.macy@xxxxxxxxx>
Sender: xen-devel-admin@xxxxxxxxxxxxxxxxxxxxx
> I
> > > think
> > > this needs some kind of flag to enable/disable this behaviour.
> >
> > I thought about that, but is there an In-guest kernel debugger that
> > can set breakpoints? All I know of are stubs that require a serial
> > port. Does NetBSD's in-kernel debugger allow one to set breakpoints
> > and continue? If so I can just put the debugger option back in
> > Rules.mk.

I spoke / wrote too soon. DDB probably does this as well. Although
I've never used it. I'd be surprised if most people didn't find the
user-level gdbserver more useful and generic than in-kernel debuggers.

Rather than being a compile-time option it should be a boot-time option.

> I believe there is a kdb patch for i386 Linux, and I have intended
> to extend my x86_64 kdb patch to Xen soon.


> I had even had thoughts of an extended debugger in dom0, but have
> been too busy to think that through. Any thoughts from others on
> that?

Interesting. In the meantime, unless someone beats me to it (wishful
thinking), I'll be extending cdb into a normal stop and continue GDB

> I recall a particularly nasty AIX bug that I worked on once
> on an S390 machine, the debugger in the nucleus (on VM/ESA) allowed
> me to set a watchpoint outside the guest and made a memory corruption
> problem MUCH easier to track down :)

That sounds more like what I've implemented than an in-kernel solution.


SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
Xen-devel mailing list