Changes between Version 11 and Version 12 of Tools/Gdb Server
- Timestamp:
- Feb 4, 2009, 9:53:56 PM (15 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Tools/Gdb Server
v11 v12 125 125 * When using the `continue` command, all processors resume at the same time. 126 126 * 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) 127 * Processors are stopped when an exception occurs. (This can be changed, see advanced commands) 127 128 128 129 === Advanced commands === … … 132 133 * The processor (thread id) used for step by step execution may be forced for the next '''single step''' operation: 133 134 {{{(gdb) monitor stepcpu 1}}} 134 * 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):135 {{{(gdb) monitor except 12}}}135 * 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 disables exception catching for thread id 2 (processor 1): 136 {{{(gdb) monitor except 0 2}}} 136 137 * The gdb protocol debug mode may enabled to dump interaction between client and server: 137 138 {{{(gdb) monitor debug 1}}}