Avi Levy wrote: > Hello, > > Since my last CVS update of simgear and flightgear two weeks ago, I get the > following runtime error after a succesfull compile.
Update again. 2 weeks ago is way outdated. When reporting a problem with CVS, try to update before to see if it has been fixed. I don't have any problem with my MSVC 7 build. > > "Unhandled exception at 0x0063ae54 in FlightGear.exe: 0xC0000005: Access > violation reading location 0x00000000." > > The debugger traces it back to the piece of code at the bottom of this post. > My question is, anybody else having this problem? Since I am using MSVC 7, I > presume that any changes made to config.ac, makefiles etc, will not be > reflected in my MSVC project files. Is there any way to keep them up-to-date There is a perl script that generate MSVC 6 dsp files. You'd better update my hand. Usually, mismatch result in unresolved external, so you can fix it at build time and with no surprise. > according to the makefile? Also, since I see threading is standard on, > trying that with MSVC results in a pthread.h not found. Is there an external > lib that I need to build to use pthread on windows? Threading was an option before and works well. It is still an option but on by default now. FG will get smoother with this : http://sources.redhat.com/pthreads-win32/ You will have to add ENABLE_THREADS in the predefined macros. > > Greetings, > > Avi > > Code: > /////////////////////////////////////////////////////////////////// > > // Initialize the TG scenery subsystem. > > //////////////////////////////////////////////////////////////////// > > globals->set_scenery( new FGScenery ); > > globals->get_scenery()->init(); What's wrong in that code ? a null pointer ? where ? Regards, -Fred _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
