Dave Perry writes > > Here is the gdb text after the model is complete to the segfault: > > > leave NewTgtAirportInit()start of fgInitProps() > > end of fgInitProps() > > [New Thread 8192 (LWP 1557)] > > > > Program received signal SIGSEGV, Segmentation fault. > > [Switching to Thread 8192 (LWP 1557)] > > 0x082b9bfc in ssgContext::forceBasicState() (this=0x8aa6fe0) > > at ssgContext.cxx:101 > > 101 if ( ovState != NULL ) > > (gdb) q > > The program is running. Exit anyway? (y or n) > > Is this enough, or did I not use the right gdb commands?
please enter 'backtrace full' in the gdb window immediately after gdb reports the Segmentation fault and post the results Note entering 'help backtrace' in the gdb window will give you an explanation of what we are doing Norman _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
