Difference between revisions of "HowTo:Use GDB"

From VsWiki
Jump to: navigation, search
m (arrow links)
Line 2: Line 2:
 
| previous=[[HowTo:Cygwin Compiling|Compiling with Cygwin]]
 
| previous=[[HowTo:Cygwin Compiling|Compiling with Cygwin]]
 
| up=[[HowTo]]
 
| up=[[HowTo]]
| next=[[HowTo:Compile Wings3d from CVS|Compiling Wings3d]]
+
| next=[[HowTo:Use Dr Watson|Use Dr Watson]]
 
}}
 
}}
 
----
 
----
Line 38: Line 38:
 
| previous=[[HowTo:Cygwin Compiling|Compiling with Cygwin]]
 
| previous=[[HowTo:Cygwin Compiling|Compiling with Cygwin]]
 
| up=[[HowTo]]
 
| up=[[HowTo]]
| next=[[HowTo:Compile Wings3d from CVS|Compiling Wings3d]]
+
| next=[[HowTo:Use Dr Watson|Use Dr Watson]]
 
}}
 
}}
  
 
[[Category:HowTo|Using GDB]]
 
[[Category:HowTo|Using GDB]]

Revision as of 22:24, 29 March 2005

arrow_left.png Compiling with Cygwin arrow_up.png HowTo Use Dr Watson arrow_right.png

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

See also

The content of this site is mostly take from this post in the forum.


arrow_left.png Compiling with Cygwin arrow_up.png HowTo Use Dr Watson arrow_right.png