Introduction to Debug Symbols
Finding debug symbols for a game can feel like opening a strategy guide: function names reveal routes through the code that would otherwise take days to trace. They do not explain every design choice, but they give a reversing project a much better starting map.
Where do debug symbols come from?
Compilers and assemblers can record names and addresses while turning source into machine code. Richer debug information may also associate instructions with source files, line numbers, types and local variables. The idea resembles a web source map, but the amount of detail varies greatly between a simple symbol table and a full debug database 1.
What are debug symbols used for?
Developers use this information to set breakpoints by function name and, when line records survive, step through source lines. A symbol table alone can name functions without recovering the original source or every local variable 1.
It also turns a crash stack of addresses into recognizable function calls, provided the symbols match the game build.
Must the symbols be inside the game executable?
No. Microsoft’s toolchain commonly stores debugging information in a separate .pdb file, keeping it out of the shipped executable 1. GNU tools can likewise split an ELF executable from its debug file; GDB can match the pair through a debug link or build ID 2. For a retail game, finding a PDB, map or debug file elsewhere can therefore be just as useful as finding an unstripped executable. Check that it belongs to the same build before trusting its addresses.
Why are debug symbols only in some games?
Teams often strip debug information from release binaries or keep it in a separate file. Sometimes an unstripped build or a companion symbol file still reaches a retail disc. The platform lists below collect examples rather than assuming every release used the same process.
Which games are likely to contain debug symbols?
Assembly projects can have labels and symbol maps too; they are not limited to C or C++ games. Early cartridge releases rarely carry large source-level debug records because space was costly, but a surviving development build or separate map can still supply names. On disc-based systems, a stray unstripped executable is easier to accommodate.
Games by Platform with debug symbols
Sony Consoles
Our Sony lists contain examples from PS1, PS2 and PSP releases, including PS2 demo discs. Their formats and the detail they retain differ, so inspect the individual game before assuming that every listed binary includes full source-level records.
Sony Playstation 1
We have a post specifically listing all the debug symbols for the PS1 here:
Sony Playstation 2
We have a post specifically listing all the debug symbols for the PS2 Demos here:
Retail PS2 examples are collected separately:
Sony Playstation Portable
Nintendo consoles
Finding symbols in older Nintendo retail cartridges can feel like looking for a needle in a haystack; sometimes all that survives is a stray developer string. GameCube discs gave developers much more room to leave build artefacts behind, and our later-console lists show how often those artefacts repay inspection.
Nintendo 64
Cartridge size gave Nintendo 64 teams a reason to leave large debug data out of retail ROMs. That is a useful expectation when searching, not proof that no retail build retained any names.
But we do have part of the Turok source code which contains them: Turok 64 Official Source Code Analysis
There has also been a number of Nintendo leaks, leaking the full source code for multiple Nintendo 64 games. Not to forget the excellent work the community is doing on reversing N64 games even without any symbols present!
Nintendo GameCube
Nintendo Wii
Nintendo Wii U
SEGA consoles
We have not yet found a Sega Saturn retail disc with debug symbols. Sega’s release practices may have played a part, but we do not have evidence for a general policy; if you find an example, please let us know.
Sega Dreamcast
Debug symbols on Microsoft consoles
Microsoft Xbox
There are also a few platforms that may have games with debug symbols but it is currently unknown:
- 3DO
- Cybiko
- GP32/GP2X/Pandora
- N-Gage
- Neo Geo X
- Sega CD/Sega 32X
Introduction Welcome to our page dedicated to the technical details of the Gamecube game 007 Agent Under Fire!
If you’re a fan of this classic first-person shooter game, you might be interested in learning more about the technical aspects that...
...
Debug symbols pretty much open a game wide open to budding verse engineers.
These files make reverse engineering almost a piece of cake, giving useful names to each of the functions in an executable and sometimes even full local variable...
...
If you are interested in reverse engineering a Gamecube game, the first step is to find out if the game has its debug symbols available, this makes it much easier to reverse as all the functions will have nice friendly... ...
I have never seen a PS1 executable bigger than 2mb, normally if they require more code they split it into multiple executables.
With memory being so precious it would be unlikely a developer would forget to strip the debug symbols...
...
Note that the order of the externals defined in this list will not reflect the order in the final linked executable, as the order here is just the order that the PSYLIB.EXE tool exports in.
LIBAPI - PS1 OS Kernel...
...
This page is dedicated to listing Playstation 2 Demo Discs that contain developer debug symbols, either embedded inside the executable or as separate .map or .sym files.
It was much more common for PS2 debug symbols to be leaked on...
...
PS2 Official Software development Kit by Sony Last known version: 3.1.0 1 First known version: 0.3.0 2 Updates were provided to licenced PlayStation developers on ps2-pro.com, where the update contained just the files that have changed and could be dropped... ...
The Sony Playstation portable used encrypted executables known as EBOOT.BIN, these are basically just an encrypted ELF file and it is possible to decrypt them with the correct tools.
Some games also ship with unencrypted executables in BOOT.BIN Finding Debug...
...
Debug symbols are normally a rare treasure sought by reverse engineers from prototypes and beta versions of games, however in the early years of the PS2 it was common for debug symbols to be left in the retail version of... ...
Retail Wii Games with Debug Symbols The following table has all the known Wii games that have debug symbols in them, if you find any more please let us know!
They are mostly ELF files with debug symbols left behind...
...
Wii U games with debug symbols A list of all the WiiU games that are known to have debug symbols are listed in the table below, eventually we want to have the count of the number of debug symbols as... ...
Debug symbols left in games make reverse engineering almost a piece of cake, giving useful names to each of the functions in an executable and sometimes even full local variable naming and source code references.
However most developers are very...
...