break pc_addr [cpu_num]
break [-cpu cpu_set] pc_addr
break [-cpu cpu_set] -trap trap_type
break [-cpu cpu_set] -red
Each breakpoint is associated with an id (printed when the breakpoint is set, by typing break with no arguments, or by the list-breakpoints command) which is used for further references to the breakpoint.
The break command without any arguments prints the list of current breakpoints.
break pc_addr cpu_num sets a breakpoint at pc_addr on the cpu cpu_num.
For the remaining forms of break, the optional flag -cpu selects a collection of cpus on which the appropriate breakpoint is set. If the -cpu flag is omitted, then the breakpoint is set on all configured cpus.
break followed by an optional -cpu flag and a pc_addr sets a breakpoint at pc_addr on the selected set of cpus.
The -trap flag sets a trap breakpoint that stops execution before a trap of type trap_type is taken on the selected set of cpus.
The -red flag sets a RED state breakpoint that stops execution before any of the selected set of cpus enters the RED state.
Breakpoints can be removed using delete.
Breakpoints are not supported in execution-driven mode. An execution-driven timing model may provide its own breakpoint capability. To avoid unpredictable results, all breakpoints should be disabled prior to enabling execution-driven simulation