Difference between revisions of "HowTo:Use GDB"
m (fixed lower navbar) |
m |
||
| Line 1: | Line 1: | ||
{{NAV_Manual | | {{NAV_Manual | | ||
| previous=[[HowTo:Compile from CVS]] | | previous=[[HowTo:Compile from CVS]] | ||
| − | | up=[[ | + | | up=[[HowTos]] |
| next=[[HowTo:Use Dr Watson|Use Dr Watson]] | | next=[[HowTo:Use Dr Watson|Use Dr Watson]] | ||
}} | }} | ||
---- | ---- | ||
| − | = Using GDB with Vegastrike = | + | =Using GDB with Vegastrike= |
This page provides information on how to use GDB to help debug Vegastrike. | This page provides information on how to use GDB to help debug Vegastrike. | ||
| − | == Debugging process == | + | ==Debugging process== |
| − | === Game compilation === | + | ===Game compilation=== |
* 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> | * 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> | ||
| Line 16: | Line 16: | ||
Please make sure you have enough disk space available before doing this. Compiling Vegastrike with <code>--enable-debug</code> eats up a huge amount of disk space. | Please make sure you have enough disk space available before doing this. Compiling Vegastrike with <code>--enable-debug</code> eats up a huge amount of disk space. | ||
| − | === Run GDB === | + | ===Run GDB=== |
* Start <code>gdb</code> (GNU Debugger):<BR/><pre>gdb /path/to/vegastrike</pre> | * Start <code>gdb</code> (GNU Debugger):<BR/><pre>gdb /path/to/vegastrike</pre> | ||
| Line 31: | Line 31: | ||
</pre> | </pre> | ||
| − | == See also == | + | ==See also== |
The content of this site is mostly take from [http://vegastrike.sourceforge.net/forums/viewtopic.php?p=4688#4688 this] post in the forum. | The content of this site is mostly take from [http://vegastrike.sourceforge.net/forums/viewtopic.php?p=4688#4688 this] post in the forum. | ||
| + | |||
---- | ---- | ||
{{NAV_Manual | | {{NAV_Manual | | ||
| previous=[[HowTo:Compile from CVS]] | | previous=[[HowTo:Compile from CVS]] | ||
| − | | up=[[ | + | | up=[[HowTos]] |
| next=[[HowTo:Use Dr Watson|Use Dr Watson]] | | next=[[HowTo:Use Dr Watson|Use Dr Watson]] | ||
}} | }} | ||
| − | [[Category: | + | [[Category:HowTos|Using GDB]] |
Revision as of 18:52, 28 May 2005
 HowTo:Compile from CVS
|
 HowTos
|
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
|
HowTos
|
Use Dr Watson
|
