Reference implementation for debug
Moderator: Moderators
Reference implementation for debug
Hi. I was wondering which would be a good "reference" implementation to compare my emulation to a "proved to be correct" one. Hopefully one that prints the contents of the registers before/after every instruction, that informs the memory locations being accessed. One that prints the content of the emulation to a file or even to a terminal (as long as I can specify a break point) I heard about FCEUX. Does it meet my needs?
Re: Reference implementation for debug
The common practice as described on "Emulator tests" on the wiki is to load nestest.nes (see also manual), JSR $C000, and compare register values to a known good log produced by Nintendulator.colt wrote: ↑Mon Nov 25, 2019 12:20 pm Hi. I was wondering which would be a good "reference" implementation to compare my emulation to a "proved to be correct" one. Hopefully one that prints the contents of the registers before/after every instruction, that informs the memory locations being accessed. One that prints the content of the emulation to a file or even to a terminal (as long as I can specify a break point) I heard about FCEUX. Does it meet my needs?