SCRYDOSBox-XReferenceBreakpointsAlso in MAME

The Breakpoints tools

These tools set breakpoints and watches and keep them. Each is saved as you named it, a symbol or an address, so the server sets it again at start and after symbols_load, even after a rebuild moved the code.

The tools call a saved breakpoint or watch a declaration, as in declaration_list. The debugger holds what is set now; the saved breakpoints file holds what you asked for. What they share is in REFERENCE.md, Breakpoints and watches.

A registerpoint (regpoint in the tool names) is a stop when a condition on the registers comes true. While the program runs nothing can be set: what you ask is saved, reads pending, and is set at the next stop. A count, capture or freeze watch is the exception: it is refused until the program stops.

What each state means

Every reply of these tools, and every row they list, carries a state.

state what it means
armed Set in the debugger and able to fire.
pending Declared while the program runs, set at its next stop.
counted A control breakpoint. Nothing is set between runs: run_to sets it, counts it and removes it.
evaluated A show watch. Nothing is set in the debugger: the value is read at every stop.
unresolved Its symbol is not in the loaded symbol table. It stays saved and sets nothing until a table has it.
ambiguous Its name matches several symbols.
unarmable It cannot be set at this stop. why says what it waits for.
null_pointer A watch through a pointer that reads zero. It stays saved and is looked up again at every stop.
stale A raw SEG:OFF that no loaded symbol table vouches for. It stays saved and is not set until you declare it again.
orphan Saved with no record of the session that made it. Clear it by its ref, or declare it again to adopt it.
gone Saved, but the debugger no longer lists its row.

A row also says inherited: true when an earlier session saved it. foreign lists debugger rows the server did not set, such as one typed through debug: they are listed and never deleted.

The tools