On 24 Apr 2012, at 12:07, Renk Thorsten wrote: > 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.
Okay, then I realise this isn't useful for you, but I'm stumped why it crashes for you. In particular, the hashForAirport function is being passed something that looks like a valid pointer (I think), and it crashing on a line that should only really happen if the pointer is invalid, or there's other memory corruption going on. Again, I realise this doesn't help you, I'm just confused by the failure mode. James ------------------------------------------------------------------------------ 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
