On 25 Oct 2009, at 21:24, Alex DaHUND wrote: > Now I was able to make some backtraces (http://nopaste.org/p/ > aPZTtaYYX). Jester pointed out, that this could be a problem of the > optimisation during the build process and advised me to configure SG > and FG with option CXXFLAGS="-g -O0". He was right, with those > binaries I wasn't able to reproduce the crash anymore. > > At the moment I am using binaries configured with CXXFLAGS="-g -O2 - > march=native" (which is athlon-xp here) and it seems a bit more > stable now. FG still crashed on some testflights across the zero > meridian, but at least not on all flights. I will try to collect > some more METAR-strings which causes troubles and some more > backtraces as well.
If it's an optimisation-related bug, tracing it is going to be pretty awful. That said, the crash seems rather widespread for a straight compiler issue. I'm also surprised that a compiler bug would change frequency based on compile options. Assuming you have a set of compiler options which definitely trigger a crash, my advice would be to to a binary CVS search (unfortunately, this has to include both SG and FG, and a clean rebuild each time, probably). Start with a point a year ago and see what happens - then six months forward or back, then three months, and so on. We also need to establish what range of GCC versions might be affected. I hate optimiser bugs :( James ------------------------------------------------------------------------------ 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
