As the fast interpreter uses an instruction loop to execute SH2 opcodes, the debugger isn't working as there's no detection of opcode state during the loop execution.
So when using the "Next" button in the debugger, the core stops at the end of the loop instead of stopping at the next instruction ...
Careful of the performance hit ...
As the fast interpreter uses an instruction loop to execute SH2 opcodes, the debugger isn't working as there's no detection of opcode state during the loop execution. So when using the "Next" button in the debugger, the core stops at the end of the loop instead of stopping at the next instruction ... Careful of the performance hit ...