Changes between Version 18 and Version 19 of Tools/Gdb Server

Timestamp:

Nov 25, 2009, 5:01:29 PM (14 years ago)

Author:

becoulet

Comment:

--

Tools/Gdb Server

@@ -134 +134 @@
 {{{
 (gdb) monitor calltrace 0         # disable for all processors
-(gdb) monitor calltrace 1 2       # enable for thread 2, processor 1
+(gdb) monitor calltrace 1 2       # enable for thread 2 (processor 1)
 }}}
  * The processor (thread id) used for step by step execution may be forced for the next '''single step''' operation:
@@ -140 +140 @@
 (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 !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. Exception catching is enabled by default but can be disabled globaly by adding the `X` flag to the the `SOCLIB_GDB` environment variable.
 {{{
 (gdb) monitor except 1            # enable for all processors
-(gdb) monitor except 0 2          # disable for thread 2, processor 1
+(gdb) monitor except 0 2          # disable for thread 2 (processor 1)
 }}}
  * An alternative way to set hardware watch point range is provided to bypass the sometime annoying gdb client watch point feature. It can be used to modifiy directly the read and write watching intervals. The following commands set a 4 bytes (default is cpu register width) read/write watch interval at 0x12345678 and then excludes read watching for 32 bytes range at 0x12345000. These watch points will be unknown to the gdb client and will be lost when the simulation terminates.