nesdev.org

Nintendulator has become my all-out favorite emulator for testing and debugging my projects.

Is there a way, using Nintendulator, where I can generate a list showing the sequence of addresses that run on the Program Counter up to the CPU locking from a bad opcode? I've tried looking into the Dump CPU, Start Log, and Stop Log options (it seems like one of those is what I'd use, but I have no idea), but none are doing anything. And I'm not finding any write-ups explaining what they are for or how exactly to use them.

The readme for Nintendulator says the following: "...debug memory dumps are now stored within the currently logged in user's Application Data folder rather than within the program's own directory." This may have to do with me using Windows 7 64-bit, but I cannot find such a folder (Application Data) anywhere on my hard drive.

Also, if I can figure out a way to do this it would be helpful in finding a lot of stuff, but specifically the bug I'm dealing with right now is somewhere in my code the PC gets set to $0000. I'm thinking it's a bank swapping error, but obviously I'm not sure yet. Now anyone should see why a list showing what the PC hit up to that point would be handy. (In other words, where was the PC before it jumped to $0000? What set it to that before jumping and why? That's what I'm trying to debug.)

Yeah, just press Start Log, then run your program, when it halts press Stop Log.

The AppData directory is by default hidden, the easiest way to reach it is to press Win+R to open the Run dialog and type %appdata% in there. The log is under the directory Nintendulator/Dumps.

AWESOME! I got it. Thanks thefox.

bigjt_2 wrote:The readme for Nintendulator says the following: "...debug memory dumps are now stored within the currently logged in user's Application Data folder rather than within the program's own directory."

AppData is intended for things that are regarded as "inside an app", such as preference files or downloaded e-mail messages. It appears from those human interface guidelines that I've read that memory dumps should use a Save As file chooser, or possibly in Saved Games under Vista and later.

Interesting. Yeah, I was wondering why I couldn't find it using the standard search, even among hidden files. Just one more of those tidbits I'm accumulating.

C:\>set | findstr APPDATA
APPDATA=C:\Users\MYUSERNAME\AppData\Roaming
LOCALAPPDATA=C:\Users\MYUSERNAME\AppData\Local

(OS = Windows 7, 64-bit)