Difference between revisions of "HowTo:Use GDB"
m (changed nav to link with HowTo:Compile_from_CVS) |
m (fixed lower navbar) |
||
| Line 36: | Line 36: | ||
---- | ---- | ||
{{NAV_Manual | | {{NAV_Manual | | ||
| − | | previous=[[HowTo: | + | | previous=[[HowTo:Compile from CVS]] |
| up=[[HowTo]] | | up=[[HowTo]] | ||
| next=[[HowTo:Use Dr Watson|Use Dr Watson]] | | next=[[HowTo:Use Dr Watson|Use Dr Watson]] | ||
Revision as of 02:36, 8 April 2005
 HowTo:Compile from CVS
|
 HowTo
|
Use Dr Watson 
|
Contents
Using GDB with Vegastrike
This page provides information on how to use GDB to help debug Vegastrike.
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 Vegastrike with --enable-debug eats up a huge amount of disk space.
Run GDB
- Start
gdb(GNU Debugger):gdb /path/to/vegastrike
- Start the game by typing 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.
| HowTo:Compile from CVS
|
HowTo
|
Use Dr Watson
|
