> > It would be interesting to see what the back trace is with > > optimization turned on. > > Absolutely - unfortunately, for whatever reason, none of the people > who can easily generate a backtrace, have been able to reproduce the > crash - I've tried, Jester has tried, and assorted others on IRC.
Hi Curtis and James and others, I am sorry, I was a bit tired last night and might not phrased myself clearly. Also I am not a coder and maybe just don't understand what you mean. But the backtraces I made actually are with optimisation turned on. Well, I built the binaries without any options on this and therefore they are -O2 by default (as far as I was able to follow Jesters explanation). Here the link again: http://nopaste.org/p/aPZTtaYYX In the meantime I have installed valgrind and I am doing my first steps with it. A first trial run turned out to be very good, I already saw the scenery ten minutes after starting it. ;-) My gcc version is: 4.3.2 (Debian 4.3.2-1.1) And enclosed you'll find the .fgfsrc file containing the options I had the day I encountered that problem the first time. Except the change for the METAR, this one replaced the real-weather-fetch. Please let me know if you need more info, as I said, I am not a coder so don't really know what to look for. Thanks Alex -- Alex D-HUND <f...@beggabaur.de>
.fgfsrc.zmcrash
Description: Binary data
------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference
_______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
