From: Mukesh Rathor <mukesh.rathor@oracle.com>
To: 고영근 <ykGo@os.korea.ac.kr>
Cc: xen-devel@lists.xen.org
Subject: Re: Xen domU module debugging using GDBSX
Date: Mon, 19 May 2014 12:17:50 -0700 [thread overview]
Message-ID: <20140519121750.047577d6@mantra.us.oracle.com> (raw)
In-Reply-To: <CAMiTO_5tyaNn27Ab-K5EPvCfk6bB=RwRQ9sY1cj_Hfid2SJiQw@mail.gmail.com>
On Mon, 19 May 2014 16:40:59 +0900
고영근 <ykGo@os.korea.ac.kr> wrote:
> I think the module symbols are not properly inserted although I added
> the module.ko file using add-symbol-file command.
> Can you explain the way to debug domU module in detail? The readMe
> file is not sufficient. Any other references might be good too
gdbsx is the backend to gdb. The issues are on gdb front end. Most likely
you just need to clean the entire tree and rebuild, as addresses are not
matching. You can just build in the module too and not have to deal
with loading symbols then.
Mukesh
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
prev parent reply other threads:[~2014-05-19 19:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-21 2:29 Xen domU module debugging using GDBSX 고영근
2014-04-22 18:30 ` Mukesh Rathor
2014-05-19 7:40 ` 고영근
2014-05-19 19:17 ` Mukesh Rathor [this message]
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=20140519121750.047577d6@mantra.us.oracle.com \
--to=mukesh.rathor@oracle.com \
--cc=xen-devel@lists.xen.org \
--cc=ykGo@os.korea.ac.kr \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).