Debug: Difference between revisions
Jump to navigation
Jump to search
Doom64hunter (talk | contribs) mNo edit summary |
Doom64hunter (talk | contribs) mNo edit summary |
||
| Line 3: | Line 3: | ||
Prints <number> to the game log file and triggers a breakpoint if the binary has been compiled with `RELEASE=0`. | Prints <number> to the game log file and triggers a breakpoint if the binary has been compiled with `RELEASE=0`. | ||
Only useful for debugging if the process is attached to a debugger like gdb. | Only useful for debugging if the process is attached to a debugger like gdb. If not attached to a debugger, the game will simply close upon encountering the instruction. | ||
[[Category:Duke3D 1.3/1.5 commands]] | [[Category:Duke3D 1.3/1.5 commands]] | ||
Latest revision as of 08:40, 6 September 2023
debug <number>
Prints <number> to the game log file and triggers a breakpoint if the binary has been compiled with `RELEASE=0`.
Only useful for debugging if the process is attached to a debugger like gdb. If not attached to a debugger, the game will simply close upon encountering the instruction.