| |
|
 |
|
 |
|
|
|
| |
|
|
xen-devel
Re: [Xen-devel] please help about gdbsx
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@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
|
|
| |
|
Home