SCRYMAMEReferenceRunAlso in DOSBox-X
The Run tools
These tools let the program run and stop it again: to an address, for a number of frames, one instruction at a time, or with no deadline. Most other tools read the machine only while it is stopped, and REFERENCE.md says which ones answer while it runs.
MAME cannot run one cpu alone. Every run and every step goes through the cpu the debugger is showing, called the visible cpu on this page. Every other cpu runs its share of the same emulated time meanwhile.
What every stop returns
A reply that ends at a stop carries the same readings whatever the call was about, because a stop is where the next question starts.
cause: what stopped the machine, by name: the target, a breakpoint, a watch, the end of the frames asked for.stop_seq: the number of this stop in the session. The stopstartleaves is 1, andstatuscounts the same way.cpu,pc,regs,frame: the cpu that stopped, its program counter, its registers and the frame counter.instruction: the instruction atpc, asaddress,bytesandtext, withsymbolanddeltawhen a symbol is near.followingholds the next lines of the listing.errorlog: what MAME's error log gained since the last stop, aslines,lines_total,truncated,markandhow. The field is not namedlog.watches: every watch and what it saw.watch_hitorregpoint_hitdescribes the one that stopped the machine.
cause also names a breakpoint, a watch or a registerpoint typed through debug, with the bpclear, wpclear or rpclear command that removes it. It writes that row's number as 0x hex, because MAME's console reads a bare D0 or A as a register.
A breakpoint names a stop only on its own cpu, since two cpus run two programs. A registerpoint, MAME's stop on a register condition, fires at every instruction while its condition holds, so regpoint_hit carries a note that it is still armed. A control, the often-run address run_to counts, never counts as a stop.
The tools
run_toRun until the program reaches an address, or a screen of the screen map, and stop there.run_forRun for a number of frames or milliseconds of emulated time and come back stopped.stepExecute a few instructions of one cpu, going into calls or over them.resumeLet the machine run, either with no deadline or waiting a while for it to stop.stopStop a running machine where it is and read where it stopped.traceRun for a number of frames or milliseconds and get every address one cpu executed, grouped by symbol.screen_waitRun until the screen shows a mapped screen, a black palette or a change of screen, and stop there.