ia64/xen-unstable

changeset 7134:3c1a91c309b8

Update GDB server documentation for crashed guests.
Signed-off-by: Keir Fraser <keir@xensource.com>
author kaf24@firebug.cl.cam.ac.uk
date Thu Sep 29 17:12:48 2005 +0100 (2005-09-29)
parents 55722e822dec
children 399436887a32
files tools/debugger/gdb/README
line diff
     1.1 --- a/tools/debugger/gdb/README	Thu Sep 29 17:12:20 2005 +0100
     1.2 +++ b/tools/debugger/gdb/README	Thu Sep 29 17:12:48 2005 +0100
     1.3 @@ -20,10 +20,18 @@ To build a debuggable guest kernel image
     1.4  
     1.5  To debug a running guest:
     1.6   1. Use 'xm list' to discover its domain id ($domid). 
     1.7 - 2. Run 'gdbserver-xen 127.0.0.1:9999 --attach $domid'
     1.8 - 3. Run 'gdb /path/to/vmlinux-syms-2.6.xx-xenU'
     1.9 + 2. Run 'gdbserver-xen 127.0.0.1:9999 --attach $domid'.
    1.10 + 3. Run 'gdb /path/to/vmlinux-syms-2.6.xx-xenU'.
    1.11   4. From within the gdb client session:
    1.12      # directory /path/to/linux-2.6.xx-xenU [*]
    1.13      # target remote 127.0.0.1:9999
    1.14      # bt
    1.15      # disass
    1.16 +
    1.17 +To debug a crashed guest:
    1.18 + 1. Add '(enable-dump yes)' to /etc/xen/xend-config.sxp before
    1.19 +    starting xend.
    1.20 + 2. When the domain crashes, a core file is written to
    1.21 +    '/var/xen/dump/<domain-name>.<domain-id>.core'.
    1.22 + 3. Run 'gdbserver-xen 127.0.0.1:9999 --file <core-file>'.
    1.23 + 4. Connect to the server as for a running guest.