> Okay, this is my fault, but I don't know why / how it's crashing for > you. Presumably you have some aircraft or nasal that makes additional > airportinfo() calls, and you've managed to find a test-case that my > testing has not encountered. Unfortunately we need to find out the > relevant bit of Nasal I guess. > > I can see it's an airportinfo() call with no arguments, which location > are you at? KSFO right? Hmmmm.
It doesn't depend - I got a crash at TNCM as well, also using both c172p and the ufo. So this must be something more generic. > Just to check, you have updated simgear as well? There's a bugfix in > there I applied at the same time. I did pull simgear, when I retry now I get 'Already up-to-date.' and I did recompile both simgear and flightgear after 'make clean' in both build directories using the same procedures I've been using since we migrated to cmake. So to my best ability to tell, my simgear is up to date. * Thorsten ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
