[Xen-changelog] Better gdb server documentation.

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

# HG changeset patch
# User kaf24@xxxxxxxxxxxxxxxxxxxx
# Node ID 08effcf0385bb6837f3e3c49517ad8798372b0fa
# Parent  52d953dcef0e882c4fc4df3afc6b4c54d30573af
Better gdb server documentation.

diff -r 52d953dcef0e -r 08effcf0385b tools/debugger/gdb/README
--- a/tools/debugger/gdb/README Mon Sep 19 15:43:26 2005
+++ b/tools/debugger/gdb/README Mon Sep 19 15:43:38 2005
@@ -2,17 +2,28 @@
 DomU GDB server for 32-bit (PAE and non-PAE) systems
 ----------------------------------------------------
 
-To build:
+Lines marked below with [*] are optional, if you want full
+source-level debugging of your kernel image.
+
+To build the GDB server:
  1. Run ./gdbbuild from within this directory.
  2. Copy ./gdb-6.2.1-linux-i386-xen/gdb/gdbserver/gdbserver-xen
     to your test machine.
 
-To debug a running domain:
+To build a debuggable guest kernel image:
+ 1. cd linux-2.6.12-xenU
+ 2. ARCH=xen make menuconfig
+ 3. From within the configurator, enable the following options:
+    # Kernel hacking -> Compile the kernel with debug info [*]
+                     -> Compile the kernel with frame pointers
+ 4. (Re)build and (re)install your xenU 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'
  4. From within the gdb client session:
+    # directory /path/to/linux-2.6.xx-xenU [*]
     # target remote 127.0.0.1:9999
     # bt
     # disass
- 5. And so on...

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