Re: [Flightgear-devel] Restore GPS compatibility with 2.10 - MSVC10

2013-06-02 Thread Alan Teeder
James Now all seems OK on both Laptop and Desk machines. I have successfully started fgfs 3 times on each machine. Thanks. Please have a beer on me. Alan -Original Message- From: James Turner Sent: Sunday, June 02, 2013 8:05 PM To: FlightGear developers discussions Subject: Re: [Flig

Re: [Flightgear-devel] Restore GPS compatibility with 2.10 - MSVC10

2013-06-02 Thread James Turner
On 2 Jun 2013, at 20:00, James Turner wrote: > I will have something for you to try shortly. Something *else* even. Specifically, if you could pull: topics/nowincrash, build, and let me know if the crashes persist / are gone, that would be very useful. Thanks, James ---

Re: [Flightgear-devel] Restore GPS compatibility with 2.10 - MSVC10

2013-06-02 Thread James Turner
On 2 Jun 2013, at 17:35, Thomas Geymayer wrote: > here is some output from valgrind (I have not included the bunch of > warnings inside the nvidia library): Thanks Thomas, I've pushed fixes for these. In all cases the un-inited vars are bools, so I would not expect them to cause memory corrupt

Re: [Flightgear-devel] Restore GPS compatibility with 2.10 - MSVC10

2013-06-02 Thread Thomas Geymayer
Hi James, here is some output from valgrind (I have not included the bunch of warnings inside the nvidia library): Startup: ==9401== Thread 1: ==9401== Conditional jump or move depends on uninitialised value(s) ==9401==at 0x8558F7: GPS::getScratchHasNext() const (gps.cxx:1308) ==9401==by