Searched refs:breakpoint (Results 1 – 11 of 11) sorted by relevance
68 # Set replay breakpoint at instruction count @icount. Execution stops70 # breakpoint. When breakpoint is set, any prior one is removed. The71 # breakpoint may be set only in replay mode and only "in the future",89 # Remove replay breakpoint which was set with @replay-break. The
91 run-gdbstub-thread-breakpoint: testthread95 --bin $< --test $(MULTIARCH_SRC)/gdbstub/test-thread-breakpoint.py, \96 hitting a breakpoint on non-main thread)138 run-gdbstub-proc-mappings run-gdbstub-thread-breakpoint \
390 CPUBreakpoint **breakpoint) in cpu_breakpoint_insert() argument411 if (breakpoint) { in cpu_breakpoint_insert()412 *breakpoint = bp; in cpu_breakpoint_insert()
1714 .help = "set breakpoint at the specified instruction count",1720 Set replay breakpoint at instruction count *icount*.1722 There can be at most one breakpoint. When breakpoint is set, any prior1723 one is removed. The breakpoint may be set only in replay mode and only1732 .help = "remove replay breakpoint",1738 Remove replay breakpoint which was previously set with ``replay_break``.
200 and the second one finds the last breakpoint in the past.204 replay forward to find the desired position or breakpoint.209 - ``reverse-continue`` (or ``rc``) - find last breakpoint in the past219 #. if breakpoint or watchpoint was met222 * replaying to the required breakpoint
171 current instruction. This means you may hit the same breakpoint a number
1102 CPUBreakpoint **breakpoint);1104 void cpu_breakpoint_remove_by_ref(CPUState *cpu, CPUBreakpoint *breakpoint);
46 * here to signify a semihosting exception, rather than a breakpoint.
168 concurrent requests. The "breakpoint" feature allows requests to be halted on
306 an example that will set a breakpoint at the start
109 - debugging operations (breakpoint insertion/removal)
Completed in 20 milliseconds