From: Mohamad Rezaei <mmrezaie@gmail.com>
To: xen-devel@lists.xensource.com
Subject: Re: how to debug xen itself?
Date: Tue, 27 Dec 2011 12:14:02 +0330 [thread overview]
Message-ID: <4EF98552.9060205@gmail.com> (raw)
In-Reply-To: <4EF714C9.5010007@gmail.com>
On 12/25/2011 03:49 PM, Mohamad Rezaei wrote:
> hi,
>
> I am trying to debug xen hypervisor through gdb, and its kgdb. I have
> compiled xen with these options: --> make debug=y optimize=0
> crash_debug=y CMDLINE="console=com1 gdb=com1 earlygdb=y" -j8
>
> I was expecting xen to stop, and wait for my gdb connection through
> serial port, but it boots up flawlessly. I am not sure what is my
> problem. Should I do something other than that.
>
> I am doing this because I want to use debugger to get better view of xen
> internals.
>
Can someone just let me know if I am doing something wrong?
--
Best Regards,
Mohamad Rezaei
next prev parent reply other threads:[~2011-12-27 8:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-25 12:19 how to debug xen itself? Mohamad Rezaei
2011-12-27 8:44 ` Mohamad Rezaei [this message]
2011-12-27 11:00 ` Tim Deegan
2011-12-27 11:50 ` Pasi Kärkkäinen
2011-12-27 12:28 ` Ian Campbell
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=4EF98552.9060205@gmail.com \
--to=mmrezaie@gmail.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 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).