Difference between revisions of "HowTo:Use GDB"
(→Game Compilation: added better newlines + code tags) |
(→Run GDB: added better newlines) |
||
| Line 17: | Line 17: | ||
=== Run GDB === | === Run GDB === | ||
| − | * Start gdb (GNU Debugger): | + | * Start <code>gdb</code> (GNU Debugger):<BR/><pre>gdb /path/to/vegastrike</pre> |
| − | |||
| − | * Start the game. Type this into the gdb-console: | + | * Start the game. Type this into the gdb-console:<BR/><pre>run</pre> |
| − | |||
* When the error occurs or it dies type | * When the error occurs or it dies type | ||
| − | + | <pre> | |
| − | + | print *this | |
| − | + | backtrace full | |
| − | + | up | |
| − | + | print *this | |
| − | + | up | |
| + | print *this | ||
| + | </pre> | ||
== See Also == | == See Also == | ||
Revision as of 17:17, 22 March 2005
 Editing News
|
 HowTo
|
Checkout CVS 
|
Contents
Using GDB with Vega Strike
This page provides information on how to use GDB to help debug Vega Strike.
Debugging Process
Game Compilation
- First you have to configure Vegastrike with the
--enable-debugoption in addition to your others:./configure <your other parameters> --enable-debug
- Then
makeyour Vegastrike binary:make
Please make sure you have enough disk space available before doing this. Compiling Vega Strike with --enable-debug eats up a huge amount of disk space.
Run GDB
- Start
gdb(GNU Debugger):gdb /path/to/vegastrike
- Start the game. Type this into the gdb-console:
run
- When the error occurs or it dies type
print *this backtrace full up print *this up print *this
See Also
The content of this site is mostly take from this post in the forum.
| Editing News
|
HowTo
|
Checkout CVS
|
