diept / bizhawk

Automatically exported from code.google.com/p/bizhawk
0 stars 0 forks source link

PCEngine Debugger doesn't respond to breakpoints #454

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. Load PCEngine/TurboGrafx16 game (e.g. CraterMaze)
2. Set breakpoint on known address for Read/Write/Execute (1B0C)
3. Play game, causing the value to change (Visible in RAM Search)

What is the expected output? What do you see instead?
I expect the game would pause after changing the value, allowing me to use the 
debugger to trace through the code near that point.

Instead, nothing happens.

What version of the product are you using? On what operating system?
1.11 on Windows 8.1 (installed the prereq pack first).

Please provide any additional information below.
Setting the break points on other values *does* work.

E.g.
In debugger, right click an instruction and click "add breakpoint" (9671 
Execute Pause).

Unpause game and continue to play.

Game pauses again 1 frame later at execution of 9671.

Perhaps just Read/Write breakpoints are broken?

Original issue reported on code.google.com by GoMeer...@gmail.com on 21 Jul 2015 at 5:00

GoogleCodeExporter commented 8 years ago
1B0C is an address within the "main memory" aka work ram etc.
3B0C is where it's mapped at on sysbus. Add the breakpoint there.
See https://github.com/TASVideos/BizHawk/issues/462

Original comment by zero...@zeromus.org on 22 Jul 2015 at 2:11