Difference between revisions of "User:Wirser:wcudir"

From VsWiki
Jump to: navigation, search
Line 1: Line 1:
#redirect [[User:Wirser]]
+
[[Category:HowTo]]
 +
= Game HowTos =
 +
 
 +
== Compile the Vega Strike sourcecode ==
 +
* [[HowTo:vsVCPP Compiling|Compiling from SVN under Visual C++]]
 +
* [[HowTo:vsCygwin Compiling|Compiling from SVN under Cygwin]]
 +
* [[HowTo:vsFedora Compiling|Compiling from SVN under Fedora Core]]
 +
* Debug a Vega Strike Compilation
 +
** [[HowTo:Use GDB|Debugging on Linux using GDB]]
 +
** [[HowTo:Use Dr Watson|Debugging on Windows using Dr Watson]]
 +
=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 <code>--enable-debug</code> option in addition to your others:<BR/><pre>./configure <your other parameters> --enable-debug</pre>
 +
 
 +
* Then <code>make</code> your Vegastrike binary:<BR/><pre>make</pre>
 +
 
 +
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===
 +
* Start <code>gdb</code> (GNU Debugger):<BR/><pre>gdb /path/to/vegastrike</pre>
 +
 
 +
* Start the game by typing this into the gdb-console:<BR/><pre>run</pre>
 +
 
 +
* When the error occurs or it dies type
 +
<pre>
 +
print *this
 +
backtrace full
 +
up
 +
print *this
 +
up
 +
print *this
 +
</pre>

Revision as of 23:53, 1 September 2006

Game HowTos

Compile the Vega Strike sourcecode

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-debug option in addition to your others:
    ./configure <your other parameters> --enable-debug
  • Then make your 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