Jonathan Polley writes: > I updated plib, SimGear, and FlightGear before rebuilding. I cleaned > everything on Windows because there were some changes to plib headers > (MSVC isn't always smart enough to properly handle header changes if > they are not in YOUR project). I haven't cleaned the MacOS build > because gcc hasn't had such problems.
Strange ... the line numbers in the back trace were definitely wrong. Did you build everything with "-g"? Regards, Curt. > > Jonathan Polley > > On Tuesday, November 12, 2002, at 06:43 AM, Curtis L. Olson wrote: > > > Just to double check, David made a change to SimGear and to the some > > of the aircraft config files yesterday. Without the change to > > simgear, flightgear will crash on startup. > > > > If that's not it, then we'll have to take a closer look, although your > > line numbers don't make sense in your back trace ... > > > > Regards, > > > > Curt. > > > > > > Jonathan Polley writes: > >> I just updated from CVS for both the Mac and Windows and got the same > >> error when I tried to run. The Mac traceback is as follows: > >> > >> > >> > >> Exception: EXC_BAD_ACCESS (0x0001) > >> Codes: KERN_PROTECTION_FAILURE (0x0002) at 0x00000006 > >> > >> Thread 0 Crashed: > >> #0 0x000525f8 in ssgContext::forceBasicState() > >> (ssgContext.cxx:103) > >> #1 0x00038464 in ssgCullAndDraw(ssgBranch*) (ssg.cxx:273) > >> #2 0x0000427c in fgRenderFrame() (main.cxx:2143) > >> #3 0x00006284 in fgMainLoop() (main.cxx:271) > >> #4 0x90163888 in __CFRunLoopDoTimer > >> #5 0x901493e0 in __CFRunLoopRun > >> #6 0x9018157c in CFRunLoopRunSpecific > >> #7 0x92ba34cc in RunCurrentEventLoopInMode > >> #8 0x92bb32f4 in ReceiveNextEventCommon > >> #9 0x92bda280 in BlockUntilNextEventMatchingListInMode > >> #10 0x93082184 in _DPSNextEvent > >> #11 0x930ccf84 in -[NSApplication > >> nextEventMatchingMask:untilDate:inMode:dequeue:] > >> #12 0x930ca500 in -[NSApplication run] > >> #13 0x94fd9110 in glutMainLoop > >> #14 0x00008c7c in mainLoop(int, char**) (main.cxx:1746) > >> #15 0x00008dd4 in main (main.cxx:1834) > >> #16 0x00002b5c in _start (crt.c:267) > >> #17 0x000029dc in start > >> > >> > >> The error was in the same routine, so I am assuming that there is > >> something uninitialized somewhere. The bad pointer was in slightly > >> different lines of code, though: > >> > >> if ( ovState != NULL ) > >> ovState -> force () ; <--- Windows Crashes > >> else > >> basicState -> force () ; <--- Mac Crashes > >> > >> Windows died where it did because ovState contained the Windows > >> non-zero invalid pointer value (0xcacacaca). > >> > >> Jonathan Polley > >> > >> > >> _______________________________________________ > >> Flightgear-devel mailing list > >> [EMAIL PROTECTED] > >> http://mail.flightgear.org/mailman/listinfo/flightgear-devel > > > > -- > > Curtis Olson IVLab / HumanFIRST Program FlightGear Project > > Twin Cities [EMAIL PROTECTED] [EMAIL PROTECTED] > > Minnesota http://www.menet.umn.edu/~curt > > http://www.flightgear.org > > > > _______________________________________________ > > Flightgear-devel mailing list > > [EMAIL PROTECTED] > > http://mail.flightgear.org/mailman/listinfo/flightgear-devel > > > _______________________________________________ > Flightgear-devel mailing list > [EMAIL PROTECTED] > http://mail.flightgear.org/mailman/listinfo/flightgear-devel -- Curtis Olson IVLab / HumanFIRST Program FlightGear Project Twin Cities [EMAIL PROTECTED] [EMAIL PROTECTED] Minnesota http://www.menet.umn.edu/~curt http://www.flightgear.org _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
