User:Wirser:wcudir

Compile the Vega Strike sourcecode

• Compiling from SVN under Visual C++
• Compiling from SVN under Cygwin
• Compiling from SVN under Fedora Core
• Compiling from SVN under SUSE
• Compiling from SVN under UMBUNTU
• Compiling from SVN under DRAPPER
• Compiling from SVN under LFS
• Compiling from SVN under OTHER
• Debug a Vega Strike Compilation
  • Debugging on Linux using GDB
  • 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 --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

Using Dr Watson with Vegastrike

When running Vegastrike on Windows, getting a backtrace from the Dr. Watson utility can help debug crashes. To set up Dr. Watson, we first need to change the type of log it dumps, and the location.

Launch Dr. Watson. The easiest way to do this is by opening the "Run" dialogue from the start menu and typing in

drwtsn32

Otherwise, it should be located in c:\windows\system32

Change the location of its output somewhere convenient, and set "Crash Dump Type" to Mini (which is human-readable). Of course, "Create Crash Dump File" must be checked off, and enabling "Dump Symbol Table" and "Dump All Thread Contents" would probably be a good idea.

Then you should get a log produced when Vegastrike crashes. Please submit this with your bug report.