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
Curt,
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
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
Jonathan Polley wrote:
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
Andy,
That fixed the problem. Thanks!
Jonathan Polley
On Tuesday, November 12, 2002, at 03:21 PM, Andy Ross wrote:
Jonathan Polley wrote:
I updated plib, SimGear, and FlightGear before rebuilding. I cleaned
everything on Windows because there were some changes to plib headers
(MSVC
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 0x0006
Thread 0 Crashed:
#0 0x000525f8 in ssgContext::forceBasicState()