On Dec 30, 2007 10:01 AM, Jason Cole <> wrote:

>
> Curt,
>
> The file does exist, tried running it with gdb with the following results:
>
> warning: Missing the separate debug info file:
> /usr/lib/debug/.build-id/08/47e52d609d30b0be7916c20f54baa732dff44f.debug
>
> warning: Missing the separate debug info file:
> /usr/lib/debug/.build-id/e3/3448de964a5ca97b70edbdcea227c6ea5d3657.debug
> [New Thread 24832912 (LWP 798)]
> [New Thread -1208404240 (LWP 795)]
>  Model Author:  Unknown
>  Creation Date: 2002-01-01
>  Version:       $Id: c172p.xml,v 1.18 2007-01-15 12:50:45 ehofman Exp $
>  Description:   Cessna C-172
> [New Thread 54573968 (LWP 799)]
> [Thread 54573968 (LWP 799) exited]
> [New Thread 54573968 (LWP 800)]
> [New Thread 68856720 (LWP 801)]
>
> Program received signal SIGSEGV, Segmentation fault.
> [Switching to Thread -1208404240 (LWP 795)]
> 0x00000000 in ?? ()
> (gdb)
>
>
> Tried to compile Flight Gear with debug symbols via
> ./configure CFLAGS=-g CXXFLAGS=-g LDFLAGS=-g
> make
> make install
>
> but gdm still stays the same thing. Am I doing it right?
>
> Plus I have reinstalled my nvidia drivers.
>
> and to answer Roberts question yes i have tried with out the joystick
> plugged in, but to no avail.
>
> Cheers,
> Jason.
>
>
After the crash, type the command "backtrace" within gdb and see if that
gives you info about the call stack at the time of the crash.

-- 
Curtis Olson: http://baron.flightgear.org/~curt/
Unique text: 2f585eeea02e2c79d7b1d8c4963bae2d
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Flightgear-users mailing list
Flightgear-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-users

Reply via email to