Changes between Version 9 and Version 10 of Tools/Gdb Server

Timestamp:

Feb 4, 2009, 8:59:33 PM (15 years ago)

Author:

becoulet

Comment:

--

Tools/Gdb Server

@@ -80 +80 @@
  ''Note that you can avoid to type this command every time: you just have to copy it in a `.gdbinit` file (in the same repertory from where you are lauching gdb).''
 
+=== Processor state analysis ===
+
 The processors are now frozen. Each processor is seen as a thread by the GDB client:
 
@@ -90 +92 @@
 * 1 Thread 1 (Processor mips_iss0)  0xe010cef4 in cpu_atomic_bit_waitset (a=0x602002cc, n=<error type>)
     at /home/diaxen/projets/mutekh/cpu/mips/include/cpu/hexo/atomic.h:99
+}}}
+
+The first processor has thread id 1. A specific processor can be selected for registers examination with the `thread` command.
+
+''Note this does change processor used for single step execution though. (see advanced commands sections)''
+
+{{{
+(gdb) thread 1
+[Switching to thread 1 (Thread 1)]#0  0x6011d370 in sched_context_stop_unlock ()
 }}}
 
@@ -110 +121 @@
 }}}
 
+=== Running code ===
+
+The following rules apply:
+
+ * All the managed processors are frozen at the same time when the gdb client prompt is displayed.
+ * When using the `continue` command, all processors resume at the same time.
+ * Single step execution is '''only''' performed on the processor which was interrupted. User selection of a different processor for data examination with the `thread` command does '''not''' change this. (see advanced commands section below)
+
+=== Advanced commands ===
+
+The gdb client offers a easy way to send server specific data though the `monitor` command. Our GdbServer takes advantages of the `monitor` command to provide useful advanced features:
+
+ * The processor (thread id) used for step by step execution may be forced for the next '''single step''' operation:
+{{{(gdb) monitor stepcpu 1}}}
+ * The GdbServer may be instructed to break on processor exception or to let the processor jump in its exception handler transparently. When used with an extra parameter, this setting can apply to a single processor instead of all. The following command enable exception catching for thread id 2 (processor 1): 
+{{{(gdb) monitor except 1 2}}}
+ * The gdb protocol debug mode may enabled to dump interaction between client and server:
+{{{(gdb) monitor debug 1}}}
+
 More informations on using the GDB client can be found on the [http://sourceware.org/gdb/ The GNU Project Debugger] home page.
+