[Xen-changelog] Update GDB server documentation for crashed guests.

[Xen patchbot -unstable <patchbot-unstable@xxxxxxxxxxxxxxxxxxx>]

# HG changeset patch
# User kaf24@xxxxxxxxxxxxxxxxxxxx
# Node ID 3c1a91c309b856e7a366760bda40afece28d167d
# Parent  55722e822dec76295366192bd7bbc8f9057930c3
Update GDB server documentation for crashed guests.
Signed-off-by: Keir Fraser <keir@xxxxxxxxxxxxx>

diff -r 55722e822dec -r 3c1a91c309b8 tools/debugger/gdb/README
--- a/tools/debugger/gdb/README Thu Sep 29 16:12:20 2005
+++ b/tools/debugger/gdb/README Thu Sep 29 16:12:48 2005
@@ -20,10 +20,18 @@
 
 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.

_______________________________________________
Xen-changelog mailing list
Xen-changelog@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-changelog