Troubleshooting EDuke32: Difference between revisions
Jump to navigation
Jump to search
Hendricks266 (talk | contribs) Created page with "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 ..." |
Hendricks266 (talk | contribs) No edit summary |
||
| Line 1: | Line 1: | ||
==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): | 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...]'' | gdb --args mapster32.exe ''[additional arguments...]'' | ||
Revision as of 15:56, 20 January 2012
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.