Difference between revisions of "HowTo:Use GDB"
(add page) |
m |
||
| Line 10: | Line 10: | ||
== Debugging Process == | == Debugging Process == | ||
=== Game Compilation === | === Game Compilation === | ||
| − | * First you have to configure | + | * First you have to configure Vega Strike with the '''--enable-debug''' option in addition to your other options: |
./configure <your other parameters> --enable-debug | ./configure <your other parameters> --enable-debug | ||
| Line 22: | Line 22: | ||
gdb /path/to/vegastrike | gdb /path/to/vegastrike | ||
| − | * Start the game. | + | * Start the game. Type this into the gdb-console: |
| − | |||
| − | |||
run | run | ||
Revision as of 07:46, 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 Vega Strike with the --enable-debug option in addition to your other options:
./configure <your other parameters> --enable-debug
- Then make your Vega Strike 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
|
