Changes between Version 15 and Version 16 of Tools/Gdb Server

Timestamp:

Feb 5, 2009, 4:16:08 PM (15 years ago)

Author:

becoulet

Comment:

--

Tools/Gdb Server

@@ -36 +36 @@
 
 {{{
-Uses('iss_wrapper', iss_t = 'common:gdb_iss', gdb_iss_t = 'common:mips32el'),
+Uses('caba:iss_wrapper', iss_t = 'common:gdb_iss', gdb_iss_t = 'common:mips32el'),
 }}}
 
@@ -43 +43 @@
 For using the !GdbServer with the legacy Iss v1 simulators (like mipsel) models, the platform description file should contain:
 {{{
-Uses('vci_xcache_wrapper', iss_t = 'common:gdb_iss', gdb_iss_t = 'common:ississ2', iss2_t = 'common:mipsel'),
+Uses('caba:vci_xcache_wrapper', iss_t = 'common:gdb_iss', gdb_iss_t = 'common:ississ2', iss2_t = 'common:mipsel'),
 }}}
 
@@ -139 +139 @@
 (gdb) monitor except 0 2
 }}}
- * 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 point will be unknown to the gdb client and will be lost when the simulation terminates.
+ * 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.
 {{{
 (gdb) monitor watch rw 0x12345678