From: Mukesh Rathor <mukesh.rathor@oracle.com>
To: gjk.liu@gmail.com
Cc: xen-devel <xen-devel@lists.xensource.com>
Subject: Re: about kdb for Xen
Date: Tue, 24 Mar 2009 19:25:56 -0700 [thread overview]
Message-ID: <49C99634.3050202@oracle.com> (raw)
In-Reply-To: <3411131.2044551237885265110.JavaMail.nabble@isper.nabble.com>
You cannot continue execution when system crashed. The only thing to do is
reboot. So go is disabled, as sometimes accidentally one might type that while
debugging.
There is some work to get gdb to debug xen, but I'm not sure what state it's in.
To assist in debugging via kdb, use gdb on xen-syms file. Then use gdb to find
matching line numbers in C file. Look at gdb manual how to do that.
Thanks,
Mukesh
gjk.liu@gmail.com wrote:
> Hi Mukesh,
>
> Why system often show"cmd not available in fatal/crashed state .....", after
> enter "go" in kdb for Xen. I have just cloned the codes from the branch.
>
> btw: Is there any other debug method for xen itself? for example, using gdb at
> source code level like linux or freebsd. I think it will be more convenient than kdb.
> You know, there are too many optimazation on code after compiled by gcc.
>
> Cheers:)
>
> Liu Jian
>
next parent reply other threads:[~2009-03-25 2:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3411131.2044551237885265110.JavaMail.nabble@isper.nabble.com>
2009-03-25 2:25 ` Mukesh Rathor [this message]
[not found] ` <8c2dc7030903242025o7a661a2yc9fa32370e7709d8@mail.gmail.com>
[not found] ` <49CC3EE1.5060807@oracle.com>
[not found] ` <8c2dc7030903270351q17449595wecd280022336de3@mail.gmail.com>
2009-03-27 20:53 ` about kdb for Xen Mukesh Rathor
[not found] ` <8c2dc7030903292141p1d08c7baiff8c53b1b4888476@mail.gmail.com>
2009-03-30 18:49 ` Mukesh Rathor
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=49C99634.3050202@oracle.com \
--to=mukesh.rathor@oracle.com \
--cc=gjk.liu@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 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.