On Sonntag 27 November 2005 11:55, Joacim Persson wrote:
> If we have the same source code version, and the same scenery version, the
> difference could lie in how our respective computer memory has been used
> lately, i.e. smells like a case of unitialised memory use (or prematurely
> freed mem). ...which a mem debugger ought to catch. (last time I had a go
> with valgrind and efence on fgfs, I ran out on swap. :P Have added some
> more swap since then. The good news is that this bug is suitable for
> hunting down in a batch run with a mem debugger -- doesn't need any user
> input.)
Hmm, I run valgrind occasionally. Nothing from that so far ...
I also have the feeling that memory management might be a problem. Even if
that probme smells like something different. That vertical plane exactly at
this place where the ufo is placed in my case might cause some problem - just
a guess.
What compiler do you use?
That extendent precision on intels cpu's covers and uncovers some problems
unpredictable - depending on some compile flags and compiler
implementations ...
Do you use some aliasing dependent compiler flags?
Hmm ...
Still thinking ...
Greetings
Mathias
--
Mathias Fröhlich, email: [EMAIL PROTECTED]
_______________________________________________
Flightgear-devel mailing list
[email protected]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d
