Crash Debugger

–Registers and Stack Screen(Crash Debugger):–

If the game would ever crash(pretty rare), either by glitches or using Gameshark codes, then it has crashed. But if the Debug Mode cheat XFYHIJERPWAL_IELWZS was entered at the Options screen (or use 810EA132 FFFF, it enables the debug cheat, with access to all chapters in chapter mode) in the bar before the game crashed the game will start displaying numbers and letters of what at first seems to be random nonsense. Wait for a moment, and if ”PRESS BUTTON” appears on screen, then it worked. Pressing A or Badvances to the ”MAIN MENU” screen. Once in there, tilt the control stick up or down to select a option. A to advance to the debug screen selected, and B to go back to Main Menu. Emulators won’t redraw the screen if the game has crashed, but if you save a state of the game at this point while the game still appears to be frozen, and then reloading it will make it appear(everything on the screen will be black, except the letters and numbers). Alternatively, you can use 81000002 1001. Turn the cheat on at any point in the game, and it’ll freeze up, making it easy enough to enter the debugger.


No need to explain this screen in extreme detail. The text on the bottom shows the date the final build was compiled on, which reads ”Jan 31 2001 13:29:42”,  and the build number is 19. However, the ”version” part i think should really say ”Build” instead of the aforementioned ”version”, unless i’m mistaken.


Self-explationary, shows the type of cause that made the game crash, as well as the Register threads. pressing c-right/left will display two more screens. What is being filled in there depends on the crash.


Shows the stack. Up and Down on Control stick scrolls through the stack, showing the newest value being pushed up on top, withthe older values being pushed down, freeing them from memory. C buttons up and down do the same thing, but only one line at a time for each press.


Depending on the type of crash, the debugger will either say ”HOSTDEBUG”, or ”RETRYCODE”.. RETRYCODE only returns you to the debugger without doing anything else, as the game has crashed. HOSTDEBUG i think once served an important role during development, as it was used for debugging purposes by the developers at Rare, to test out various things without having to go through the whole game. The code for this option is sadly missing from the ROM, as it needs an official Nintendo 64 Development Kit to function, so selecting this will make the game completely frozen, with music still playing in the background, maybe with any sound effect that was played at the time of the crash. No current known method or hack exists to enable these Debug features in the retail game, so there’s leg work to be done if the code for it is ever going to be found. I will do more research into this, in hopes of being able to make it functional.

Update: I will be doing some research on the debug text and asm instructions present in the ROM. Maybe there could be a way to activate the crash debugger itself during gameplay by constructing an asm code out of this.