AnachronautandClaude Opus 5
5fd995aa62
A breakpoint that shows every register as the program had them, waits for a key, and carries on. NOTHING IS OVERWRITTEN, and that is the design rather than a shortcut. A breakpoint poked into a running program has to replace an instruction, and putting that instruction back in order to continue is the same act as disarming the breakpoint; firing a second time would mean stepping over the restored instruction and putting the breakpoint back behind it, and this machine cannot step a single instruction. SWI is two bytes, dispatches through a vector, and its frame already holds the address after it, so RETI resumes at the next instruction with nothing to restore and nothing to re-arm. It fires every time it is reached. The price is that a breakpoint is part of the program: a build with them in has different addresses from a build without. That is the bargain every machine with a break instruction makes. Every value shown comes out of the frame rather than the registers, because by the time the handler runs the registers are the handler's. Apps/Break.asm stops twice so that the second stop is checked as well as the first. Also here, found by the test that came with it: the monitor's s wrote into whichever bank was selected, and bank 2 is the controller's own table, published read only. Writing to it was refused, and a refusal nobody catches stops the machine - so selecting the bank table to look at it and then typing s killed the session. bankPresent now keeps the whole flags byte and s declines. The recorded output of cosmosMonitor had contained that crash, having been blessed without being read. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
21 lines
173 B
Plaintext
21 lines
173 B
Plaintext
monitor
|
|
b nonsense
|
|
b 9
|
|
load greet.sbx
|
|
b program
|
|
d 2000
|
|
x 2000
|
|
b data
|
|
x 1000
|
|
b 2
|
|
x 0
|
|
s 0 FF
|
|
b program
|
|
s 8000 26 48 D1 00 26 0A D1 00 18 12
|
|
d 8000
|
|
g 8000
|
|
d 8000
|
|
exit
|
|
dir
|
|
exit
|