From: Mukesh Rathor <mukesh.rathor@oracle.com>
To: xen-devel@lists.xensource.com
Cc: andy@cs.ubc.ca, brendan@cs.ubc.ca
Subject: kdb for xen
Date: Fri, 02 May 2008 18:23:38 -0700 [thread overview]
Message-ID: <481BBE9A.4010406@oracle.com> (raw)
Hi xen folks,
It is my pleasure to announce an internal debugger for the xen hypervisor
(64bit). It's a full fledged debugger that will "halt" the system, so the
entire state can be examined. Some examples of commands:
xkdb> cpu all : see one line state of all cpus
xkdb> cpu 7 : switch to cpu 7 (the leaving cpu will pause immed)
xkdb> dd addr 32 : display 32 bytes at address in doublewords
xkdb> dr sp : display registers including special registers
xkdb> ni : single step (go over function calls)
xkdb> dom 5 : display dom 5 details
xkdb> vcpu <ptr> : display vcpu details at give "ptr"
Type "h" at the prompt for all commands and usages.
It can be downloaded from:
http://xenbits.xensource.com/ext/kdb.hg
and built by running "make kdb=y" in xen-unstable.hg/xen
FEATURES:
- set breakpoints in hypervisor
- examine/modify memory, registers, special registers, domains, vcpus, etc..
- single step, single step till jump/call, step over call to next
instruction after the call.
- examine/modify memory of a PV guest.
- set breakpoints, single step, etc... for a PV guest.
- above functionality for HVM guest if the debugger breaks into a running
HVM guest.
- breaking into the debugger will freeze the system, all CPUs will pause,
no interrupts are acknowledged in the debugger. (Hence, the wall clock
will drift)
- single step will step only that cpu.
Regards,
Mukesh Rathor
next reply other threads:[~2008-05-03 1:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-03 1:23 Mukesh Rathor [this message]
2008-05-20 21:33 ` kdb for xen Mukesh Rathor
2008-06-07 1:52 ` 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=481BBE9A.4010406@oracle.com \
--to=mukesh.rathor@oracle.com \
--cc=andy@cs.ubc.ca \
--cc=brendan@cs.ubc.ca \
--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.