You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The number of bytes that exec reports on each opcode is five. This causes RET, branch and jump opcodes to stick out like a sore thumb, because it reports bytes after the opcode as being executed when in fact they aren't.
This is both a SPC Debugger-side and a LibGME_M-side bug:
On the Lib_GME_M side, incomplete reporting would probably expose everything else when the for loop is removed and cause dots of red to appear instead of a line of them. For this reason, the reporting needs to be updated to account for all of the opcodes and all of their parameters.
The text was updated successfully, but these errors were encountered:
KungFuFurby
added a commit
to KungFuFurby/snestracker
that referenced
this issue
Mar 24, 2022
The number of bytes that exec reports on each opcode is five. This causes RET, branch and jump opcodes to stick out like a sore thumb, because it reports bytes after the opcode as being executed when in fact they aren't.
This is both a SPC Debugger-side and a LibGME_M-side bug:
https://github.com/bazzinotti/snestracker/blob/70e085b8dff0c0608ea68d07fa25eb216ec89a9c/pc/debugger/report.cpp#L13-L27
The text was updated successfully, but these errors were encountered: