Hard Light Productions Forums

Modding, Mission Design, and Coding => FS2 Open Coding - The Source Code Project (SCP) => Cross-Platform Development => Topic started by: WMCoolmon on August 24, 2005, 01:03:34 am

Title: gdb
Post by: WMCoolmon on August 24, 2005, 01:03:34 am

Rather than going through the gazillion-page menu...is there an easy way to get a stack trace, and current variable values for a stack trace? I've gotten fs2_open_d running from within it, but I had to kill it from a console as I haven't been able to run with the -windowed argument. :wtf:

Title: gdb
Post by: fizz on August 24, 2005, 02:59:31 am

What is it that didn't work with -window? I'm using it all the time.

Title: gdb
Post by: WMCoolmon on August 24, 2005, 03:00:39 am

"gdb fs2_open_d -windowed"

Title: gdb
Post by: fizz on August 24, 2005, 03:19:29 am

Try "gdb --args fs2_open_d -windowed" instead.
Otherwise gdb will interpret the -windowed as an arg for itself.

Title: gdb
Post by: WMCoolmon on August 24, 2005, 05:11:25 am

Well, that's half working. The problem now seems to be that fs2_open grabs control of the keyboard, so I can't alt-tab, and the mouse freezes with it. So every time I hit a segfault or somesuch, I have to kill gdb via one of the ttys and can't get at the console window to try and output a stack trace.

Title: gdb
Post by: fizz on August 24, 2005, 05:38:48 am

Don't forget -nograb.