Troubleshooting EDuke32 - EDukeWiki

# Troubleshooting EDuke32

From EDukeWiki
Revision as of 16:56, 20 January 2012 by Hendricks266 (talk | contribs)

## Debugging

The most insidious types of bugs are those that occur randomly and with no apparent pattern. To help the developers tracing down crashes happening this way, you could try running a debug version of the executable under the GNU debugger until the crash happens. To do this, start it like this (mapster32.exe being an example):

    gdb --args mapster32.exe [additional arguments...]

and enter the

    r

(run) command at the GDB prompt. When the program crashes, you will be taken back to the prompt. Enter

    bt

(backtrace) there. This will print out the location where the crash occurred and serve as a first diagnostic to the developers.

Retrieved from "http://wiki.eduke32.com/w/index.php?title=Troubleshooting_EDuke32&oldid=10147"