Difference between revisions of "HowTo:Use GDB"
m |
(→Game Compilation: added better newlines + code tags) |
||
| Line 10: | Line 10: | ||
== Debugging Process == | == Debugging Process == | ||
=== Game Compilation === | === Game Compilation === | ||
| − | * First you have to configure | + | * First you have to configure Vegastrike with the <code>--enable-debug</code> option in addition to your others:<BR/><pre>./configure <your other parameters> --enable-debug</pre> |
| − | |||
| − | * Then | + | * Then <code>make</code> your Vegastrike binary:<BR/><pre>make</pre> |
| − | |||
| − | Please make sure you have enough disk space available before doing this. Compiling Vega Strike with | + | Please make sure you have enough disk space available before doing this. Compiling Vega Strike with <code>--enable-debug</code> eats up a huge amount of disk space. |
=== Run GDB === | === Run GDB === | ||
Revision as of 17:12, 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
|
