Re: State of gdbsx in xen-4.0-testing.hg and debugger documentation.

[Bruce Edge <bruce.edge@gmail.com>]

[-- Attachment #1.1: Type: text/plain, Size: 1367 bytes --]

On Thu, Jul 1, 2010 at 3:08 PM, Mukesh Rathor <mukesh.rathor@oracle.com>wrote:

> On Thu, 01 Jul 2010 23:54:34 +0200
> Jeremy Fitzhardinge <jeremy@goop.org> wrote:
>
> > On 07/01/2010 10:13 PM, Mukesh Rathor wrote:
> > > Thanks for CC Konrad, I'm gazillions postings behind in catching up
> > > xen-devel.
> > >
> > > Bruce, you don't need to use the ext repo anymore as gdbsx is now
> > > merged mainline. I should update the blog post.
> > >
> > > To build a debug enabled xen image: make gdbsx=y  is all you need
> > > to do. After booting with gdbsx enabled xen, you can run gdbsx in
> > > dom0. See tools/debugger/gdbsx/README.
> > >
> >
> > I noticed when I tried gdbsx today that it doesn't seem to deal with
> > multi-vcpu guests by treating the vcpus as threads within gdb.  Is
> > there some other way to look at all the threads' contexts from within
> > gdb?
> >
> >     J
>
> Hmm... working for me. Can you please run gdbsx with -d and tar
> and send output to me?
>
> Mukesh,

Here's the output from gdbsx -d when trying to view CPUs as thread.



> BTW, what xen and guest versions?
>

xen 4.1 unstable sync'd last night
dom0:  Linux kaan-22 2.6.32.16 #1 SMP Mon Jul 12 14:00:17 UTC 2010 x86_64
GNU/Linux
domU: Same: Linux kaan-22 2.6.32.16 #1 SMP Mon Jul 12 14:00:17 UTC 2010
x86_64 GNU/Linux

Thanks for looking into this.

-Bruce


> thanks,
> M
>
>

[-- Attachment #1.2: Type: text/html, Size: 2292 bytes --]

[-- Attachment #2: screenlog.23.gz --]
[-- Type: application/x-gzip, Size: 1788 bytes --]

[-- Attachment #3: Type: text/plain, Size: 138 bytes --]

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