From: topperxin <topperxin@126.com>
To: mukesh.rathor@oracle.com
Cc: xen-devel <xen-devel@lists.xensource.com>
Subject: please help about gdbsx
Date: Tue, 7 Dec 2010 17:27:48 +0800 (CST) [thread overview]
Message-ID: <58975324.efea.12cc02880ee.Coremail.topperxin@126.com> (raw)
[-- 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
next reply other threads:[~2010-12-07 9:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-07 9:27 topperxin [this message]
2010-12-07 9:47 ` please help about gdbsx Ian Campbell
2010-12-09 12:06 ` topperxin
2010-12-09 12:12 ` Ian Campbell
2010-12-09 14:46 ` Bruce Edge
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=58975324.efea.12cc02880ee.Coremail.topperxin@126.com \
--to=topperxin@126.com \
--cc=mukesh.rathor@oracle.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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.