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

Timestamp:

Feb 4, 2009, 9:35:22 PM (15 years ago)

Author:

becoulet

Comment:

--

Tools/Gdb Server

@@ -31 +31 @@
    // With GdbServer
    soclib::caba::VciXcacheWrapper<soclib::common::GdbServer<soclib::common::Mips32ElIss> > cpu0("cpu0", 0, maptab, IntTab(0), 1,8,4, 1,8,4);
-}}}
-
-Then define the cpu as frozen directly at the boot:
-{{{
-soclib::common::GdbServer<soclib::common::Mips32ElIss>::start_frozen();
 }}}
 
@@ -125 +120 @@
 The following rules apply:
 
+ * Managed processors begin executing code at simulation startup until a gdb client connect on port 2346.
+ * Processors may be forced to start in frozen state waiting for incoming gdb connection by setting the `SOCLIB_GDB` environment variable to `START_FROZEN`.
  * 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.
@@ -135 +132 @@
  * 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): 
+ * 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 enables 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: