All of lore.kernel.org
 help / color / mirror / Atom feed
* please help about gdbsx
@ 2010-12-07  9:27 topperxin
  2010-12-07  9:47 ` Ian Campbell
  2010-12-09 14:46 ` Bruce Edge
  0 siblings, 2 replies; 5+ messages in thread
From: topperxin @ 2010-12-07  9:27 UTC (permalink / raw)
  To: mukesh.rathor; +Cc: xen-devel


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

hello mukesh
      Now,I want debug the xen domU kernel or kernel modules, I found the tools gdbsx under xen source directory. As the guide of README you wrote, I compile the xen with: 
make gdbsx=y


but I got the errors as below:
remote: Counting objects: 1857338, done.
remote: Compressing objects: 100% (292566/292566), done.
Receiving objects: 100% (1857338/1857338), 368.84 MiB | 53 KiB/s, done.
remote: Total 1857338 (delta 1554805), reused 1849232 (delta 1547905)
Resolving deltas: 100% (1554805/1554805), done.
Checking out files: 100% (30571/30571), done.
+ cd linux-2.6-pvops.git.tmp
+ git checkout xen/master
error: pathspec 'xen/master' did not match any file(s) known to git.
make[2]: *** [linux-2.6-pvops.git/.valid-src] error 1
make[2]: Leaving directory `/home/nlx/nex-4.5.4/xen'
make[1]: *** [linux-2.6-pvops-install] error 2
make[1]: Leaving directory `/home/nlx/nex-4.5.4/xen'
make: *** [install-kernels] error 1


could you give me some advice on how to solve this errors?
   thanks a lot.

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

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

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

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: please help about gdbsx
  2010-12-07  9:27 please help about gdbsx topperxin
@ 2010-12-07  9:47 ` Ian Campbell
  2010-12-09 12:06   ` topperxin
  2010-12-09 14:46 ` Bruce Edge
  1 sibling, 1 reply; 5+ messages in thread
From: Ian Campbell @ 2010-12-07  9:47 UTC (permalink / raw)
  To: topperxin; +Cc: xen-devel

On Tue, 2010-12-07 at 09:27 +0000, topperxin wrote:
> hello mukesh
>       Now,I want debug the xen domU kernel or kernel modules, I found
> the tools gdbsx under xen source directory. As the guide of README you
> wrote, I compile the xen with: 
> make gdbsx=y
> 
> 
> but I got the errors as below:
> remote: Counting objects: 1857338, done.
> remote: Compressing objects: 100% (292566/292566), done.
> Receiving objects: 100% (1857338/1857338), 368.84 MiB | 53 KiB/s,
> done.
> remote: Total 1857338 (delta 1554805), reused 1849232 (delta 1547905)
> Resolving deltas: 100% (1554805/1554805), done.
> Checking out files: 100% (30571/30571), done.
> + cd linux-2.6-pvops.git.tmp
> + git checkout xen/master
> error: pathspec 'xen/master' did not match any file(s) known to git.
> make[2]: *** [linux-2.6-pvops.git/.valid-src] error 1
> make[2]: Leaving directory `/home/nlx/nex-4.5.4/xen'
> make[1]: *** [linux-2.6-pvops-install] error 2
> make[1]: Leaving directory `/home/nlx/nex-4.5.4/xen'
> make: *** [install-kernels] error 1

This error message clearly indicates a problem building the kernel and
not gdbsx.

The fact that your kernel build tried to clone xen/master suggests you
are not building in an uptodate Xen source tree (it looks like you have
4.0.0). I recommend you use either the xen-4.0-testing.hg mercurial tree
or at a minimum update to the 4.0.1 release.

Since you only need to build the tools and not the kernels or hypervisor
you can use the tools targets as described in "make help". e.g.

 $ make gdbsx=y tools

(it looks like gdbsx=y is redundant since building gdbsx is not actually
optional, probably tools/debugger/gdbsx/README is out of date)

Ian.

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re:Re: please help about gdbsx
  2010-12-07  9:47 ` Ian Campbell
@ 2010-12-09 12:06   ` topperxin
  2010-12-09 12:12     ` Ian Campbell
  0 siblings, 1 reply; 5+ messages in thread
From: topperxin @ 2010-12-09 12:06 UTC (permalink / raw)
  To: Ian Campbell; +Cc: xen-devel


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

hi Ian
   As your suggestions, I compile the gdbsx tools independently use
   make gdbsx=y tools
   but when I executed the gdbsx on dom0, I got this error:
    ERROR:_check_hyp:Hyp is NOT enabled for gdbsx
    ERROR: failed to attach to domain:2 errno:38
   It looks like I have to recompile the xen & make it enable gdbsx.
       I just do like this: make gdbsx=y
   but I still get the error which I offered before.
   Should I use xen4.0.1? xen 4.0.0 not support gdbsx?
   our system using xen 4.0.0 
   





At 2010-12-07 17:47:44,"Ian Campbell" <Ian.Campbell@citrix.com> wrote:

>On Tue, 2010-12-07 at 09:27 +0000, topperxin wrote:
>> hello mukesh
>>       Now,I want debug the xen domU kernel or kernel modules, I found
>> the tools gdbsx under xen source directory. As the guide of README you
>> wrote, I compile the xen with: 
>> make gdbsx=y
>> 
>> 
>> but I got the errors as below:
>> remote: Counting objects: 1857338, done.
>> remote: Compressing objects: 100% (292566/292566), done.
>> Receiving objects: 100% (1857338/1857338), 368.84 MiB | 53 KiB/s,
>> done.
>> remote: Total 1857338 (delta 1554805), reused 1849232 (delta 1547905)
>> Resolving deltas: 100% (1554805/1554805), done.
>> Checking out files: 100% (30571/30571), done.
>> + cd linux-2.6-pvops.git.tmp
>> + git checkout xen/master
>> error: pathspec 'xen/master' did not match any file(s) known to git.
>> make[2]: *** [linux-2.6-pvops.git/.valid-src] error 1
>> make[2]: Leaving directory `/home/nlx/nex-4.5.4/xen'
>> make[1]: *** [linux-2.6-pvops-install] error 2
>> make[1]: Leaving directory `/home/nlx/nex-4.5.4/xen'
>> make: *** [install-kernels] error 1
>
>This error message clearly indicates a problem building the kernel and
>not gdbsx.
>
>The fact that your kernel build tried to clone xen/master suggests you
>are not building in an uptodate Xen source tree (it looks like you have
>4.0.0). I recommend you use either the xen-4.0-testing.hg mercurial tree
>or at a minimum update to the 4.0.1 release.
>
>Since you only need to build the tools and not the kernels or hypervisor
>you can use the tools targets as described in "make help". e.g.
>
> $ make gdbsx=y tools
>
>(it looks like gdbsx=y is redundant since building gdbsx is not actually
>optional, probably tools/debugger/gdbsx/README is out of date)
>
>Ian.
>
>
>
>
>_______________________________________________
>Xen-devel mailing list
>Xen-devel@lists.xensource.com
>http://lists.xensource.com/xen-devel

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

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

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

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: Re:Re: please help about gdbsx
  2010-12-09 12:06   ` topperxin
@ 2010-12-09 12:12     ` Ian Campbell
  0 siblings, 0 replies; 5+ messages in thread
From: Ian Campbell @ 2010-12-09 12:12 UTC (permalink / raw)
  To: topperxin; +Cc: xen-devel

On Thu, 2010-12-09 at 12:06 +0000, topperxin wrote:
> hi Ian
>    As your suggestions, I compile the gdbsx tools independently use
>    make gdbsx=y tools
>    but when I executed the gdbsx on dom0, I got this error:
>     ERROR:_check_hyp:Hyp is NOT enabled for gdbsx
>     ERROR: failed to attach to domain:2 errno:38
>    It looks like I have to recompile the xen & make it enable gdbsx.
>        I just do like this: make gdbsx=y
>    but I still get the error which I offered before.

Try adding "KERNELS=" to your make line, that will avoid the error
compiling the kernel.

>    Should I use xen4.0.1? xen 4.0.0 not support gdbsx?
>    our system using xen 4.0.0 

I've no idea but as a general rule using the most recent stable release
is a good idea.

Ian.

>    
> 
> 
> 
> 
> At 2010-12-07 17:47:44,"Ian Campbell" <Ian.Campbell@citrix.com> wrote:
> 
> >On Tue, 2010-12-07 at 09:27 +0000, topperxin wrote:
> >> hello mukesh
> >>       Now,I want debug the xen domU kernel or kernel modules, I found
> >> the tools gdbsx under xen source directory. As the guide of README you
> >> wrote, I compile the xen with: 
> >> make gdbsx=y
> >> 
> >> 
> >> but I got the errors as below:
> >> remote: Counting objects: 1857338, done.
> >> remote: Compressing objects: 100% (292566/292566), done.
> >> Receiving objects: 100% (1857338/1857338), 368.84 MiB | 53 KiB/s,
> >> done.
> >> remote: Total 1857338 (delta 1554805), reused 1849232 (delta 1547905)
> >> Resolving deltas: 100% (1554805/1554805), done.
> >> Checking out files: 100% (30571/30571), done.
> >> + cd linux-2.6-pvops.git.tmp
> >> + git checkout xen/master
> >> error: pathspec 'xen/master' did not match any file(s) known to git.
> >> make[2]: *** [linux-2.6-pvops.git/.valid-src] error 1
> >> make[2]: Leaving directory `/home/nlx/nex-4.5.4/xen'
> >> make[1]: *** [linux-2.6-pvops-install] error 2
> >> make[1]: Leaving directory `/home/nlx/nex-4.5.4/xen'
> >> make: *** [install-kernels] error 1
> >
> >This error message clearly indicates a problem building the kernel and
> >not gdbsx.
> >
> >The fact that your kernel build tried to clone xen/master suggests you
> >are not building in an uptodate Xen source tree (it looks like you have
> >4.0.0). I recommend you use either the xen-4.0-testing.hg mercurial tree
> >or at a minimum update to the 4.0.1 release.
> >
> >Since you only need to build the tools and not the kernels or hypervisor
> >you can use the tools targets as described in "make help". e.g.
> >
> > $ make gdbsx=y tools
> >
> >(it looks like gdbsx=y is redundant since building gdbsx is not actually
> >optional, probably tools/debugger/gdbsx/README is out of date)
> >
> >Ian.
> >
> >
> >
> >
> >_______________________________________________
> >Xen-devel mailing list
> >Xen-devel@lists.xensource.com
> >http://lists.xensource.com/xen-devel
> 
> 
> 
> ______________________________________________________________________
> 网易163/126邮箱百分百兼容iphone ipad邮件收发

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: please help about gdbsx
  2010-12-07  9:27 please help about gdbsx topperxin
  2010-12-07  9:47 ` Ian Campbell
@ 2010-12-09 14:46 ` Bruce Edge
  1 sibling, 0 replies; 5+ messages in thread
From: Bruce Edge @ 2010-12-09 14:46 UTC (permalink / raw)
  To: topperxin; +Cc: xen-devel

2010/12/7 topperxin <topperxin@126.com>:
> hello mukesh
>       Now,I want debug the xen domU kernel or kernel modules, I found the
> tools gdbsx under xen source directory. As the guide of README you wrote, I
> compile the xen with:
> make gdbsx=y
> but I got the errors as below:
> remote: Counting objects: 1857338, done.
> remote: Compressing objects: 100% (292566/292566), done.
> Receiving objects: 100% (1857338/1857338), 368.84 MiB | 53 KiB/s, done.
> remote: Total 1857338 (delta 1554805), reused 1849232 (delta 1547905)
> Resolving deltas: 100% (1554805/1554805), done.
> Checking out files: 100% (30571/30571), done.
> + cd linux-2.6-pvops.git.tmp
> + git checkout xen/master
> error: pathspec 'xen/master' did not match any file(s) known to git.
> make[2]: *** [linux-2.6-pvops.git/.valid-src] error 1
> make[2]: Leaving directory `/home/nlx/nex-4.5.4/xen'
> make[1]: *** [linux-2.6-pvops-install] error 2
> make[1]: Leaving directory `/home/nlx/nex-4.5.4/xen'
> make: *** [install-kernels] error 1
> could you give me some advice on how to solve this errors?
>    thanks a lot.
>

If you use xen-unstable, you don't need to build gdbsx by itself. It
is always built as part of the xen compilation.
After installing xen, it should end up in /usr/sbin/gdbsx on dom0.

-Bruce

> ________________________________
> 网易163/126邮箱百分百兼容iphone ipad邮件收发
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
>

^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2010-12-09 14:46 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2010-12-07  9:27 please help about gdbsx topperxin
2010-12-07  9:47 ` Ian Campbell
2010-12-09 12:06   ` topperxin
2010-12-09 12:12     ` Ian Campbell
2010-12-09 14:46 ` Bruce Edge

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.