aboutsummaryrefslogtreecommitdiffstats
path: root/tools
diff options
context:
space:
mode:
authoremellor@ewan <emellor@ewan>2005-09-30 10:50:19 +0100
committeremellor@ewan <emellor@ewan>2005-09-30 10:50:19 +0100
commite9a3ddb1b2786eb1c8917f2cd84a6267cf4504f9 (patch)
treec5256b37898f5a07b928dab39ca54b1589c4d8a6 /tools
parenta4db84d76c3f31b8549df00bc19964a0696e1ea8 (diff)
parentd8c9074e1bc8c21e0a47ef89dfa24cd1af67a766 (diff)
downloadxen-e9a3ddb1b2786eb1c8917f2cd84a6267cf4504f9.tar.gz
xen-e9a3ddb1b2786eb1c8917f2cd84a6267cf4504f9.tar.bz2
xen-e9a3ddb1b2786eb1c8917f2cd84a6267cf4504f9.zip
Merge.
Diffstat (limited to 'tools')
-rw-r--r--tools/debugger/gdb/README12
1 files changed, 10 insertions, 2 deletions
diff --git a/tools/debugger/gdb/README b/tools/debugger/gdb/README
index 43f1e60fef..0aa9d68772 100644
--- a/tools/debugger/gdb/README
+++ b/tools/debugger/gdb/README
@@ -20,10 +20,18 @@ To build a debuggable guest kernel image:
To debug a running guest:
1. Use 'xm list' to discover its domain id ($domid).
- 2. Run 'gdbserver-xen 127.0.0.1:9999 --attach $domid'
- 3. Run 'gdb /path/to/vmlinux-syms-2.6.xx-xenU'
+ 2. Run 'gdbserver-xen 127.0.0.1:9999 --attach $domid'.
+ 3. Run 'gdb /path/to/vmlinux-syms-2.6.xx-xenU'.
4. From within the gdb client session:
# directory /path/to/linux-2.6.xx-xenU [*]
# target remote 127.0.0.1:9999
# bt
# disass
+
+To debug a crashed guest:
+ 1. Add '(enable-dump yes)' to /etc/xen/xend-config.sxp before
+ starting xend.
+ 2. When the domain crashes, a core file is written to
+ '/var/xen/dump/<domain-name>.<domain-id>.core'.
+ 3. Run 'gdbserver-xen 127.0.0.1:9999 --file <core-file>'.
+ 4. Connect to the server as for a running guest.