The desmume.emulator.DeSmuME().cycle() method advances execution by one frame, but there doesn't seem to be a way to advance by one instruction. Does such a capability exist in py-desmume? I wasn't able to find one in the docs.
I tried to do some hacky stuff like setting a breakpoint using register_exec to the next instruction and pausing the emulator there, but this doesn't seem to work when the next instruction is the result of a branch.
Is there a way to accomplish this using py-desmume, and if not, would you be open to a PR that adds it? The latest desmume version seems to have expanded debugging features, so I'd be happy to take a look to see if there's somewhere the interface could hook into to get this into py-desmume. no promises that I would succeed, but I'm willing to try if you're open to it 😄 .
The
desmume.emulator.DeSmuME().cycle()method advances execution by one frame, but there doesn't seem to be a way to advance by one instruction. Does such a capability exist in py-desmume? I wasn't able to find one in the docs.I tried to do some hacky stuff like setting a breakpoint using
register_execto the next instruction and pausing the emulator there, but this doesn't seem to work when the next instruction is the result of a branch.Is there a way to accomplish this using py-desmume, and if not, would you be open to a PR that adds it? The latest desmume version seems to have expanded debugging features, so I'd be happy to take a look to see if there's somewhere the interface could hook into to get this into py-desmume. no promises that I would succeed, but I'm willing to try if you're open to it 😄 .