Closed dirkwhoffmann closed 5 months ago
To get started, I've added a new menu item, Edit->BRK
, which simulates the execution of a BRK
command. To test, I've started Final Cartridge III and entered the monitor via MON
:
Now, selecting BRK
from the Edit
menu results in the following:
@cfwdman Is this the expected behavior? If yes, the only remaining task is letting the breakpoint handler do the same as the menu item.
Additional thoughts: The intended behavior (entering the debugger when reaching a breakpoint) can already be achieved like so:
Yes, it's two additional steps (steps 2 and 3), but I prefer not to add yet another configuration option. With every new option, the emulator gets bloated more and more, which I'd like to avoid. I want to keep the emulator as lean as possible.
Fixed in v4.7b1
Would it be possible to allow for the dynamic breakpoints set by the emulator to cause the same effects in the processors emulation code as the execution of the BRK opcode? This could be an alternative option to be set in the preferences/inspector to the current "time freeze" of the whole system. This would allow then to break into a native debugger/monitor (e.g. from a cartridge)...