Since a while I couldn't use the j3cub any more. I always got a segfault
and nobody else could reproduce. I found a division by zero in one of
YASim's files. When I had fixed that, the cub worked again ... except
for the brakes. Again, nobody could reproduce. WTF?!

$ strace -fF -eopen fgfs --aircraft=j3cub 2>&1|tee /tmp/fgfs.log
...
open("/usr/local/share/flightgear/Aircraft/f16/Panels/Textures", 
O_RDONLY|O_NONBLOCK|O_LARGEFILE|O_DIRECTORY) = 6
open("/usr/local/share/flightgear/Aircraft/f16/Models", 
O_RDONLY|O_NONBLOCK|O_LARGEFILE|O_DIRECTORY) = 5
open("/usr/local/share/flightgear/Aircraft/747", 
O_RDONLY|O_NONBLOCK|O_LARGEFILE|O_DIRECTORY) = 4
open("/usr/local/share/flightgear/Aircraft/747/Models", 
O_RDONLY|O_NONBLOCK|O_LARGEFILE|O_DIRECTORY) = 5
open("/usr/local/share/flightgear/Aircraft/j22", 
O_RDONLY|O_NONBLOCK|O_LARGEFILE|O_DIRECTORY) = 4
open("/usr/local/share/flightgear/Aircraft/j22/Huds", 
O_RDONLY|O_NONBLOCK|O_LARGEFILE|O_DIRECTORY) = 5
open("/usr/local/share/flightgear/Aircraft/j22/Models", 
O_RDONLY|O_NONBLOCK|O_LARGEFILE|O_DIRECTORY) = 5
open("/usr/local/share/flightgear/Aircraft/_berg", 
O_RDONLY|O_NONBLOCK|O_LARGEFILE|O_DIRECTORY) = 4
open("/usr/local/share/flightgear/Aircraft/_berg/j3cub-set.xml", O_RDONLY) = 5
open("/usr/local/share/flightgear/Aircraft/_berg/j3cub-3d-yasim-set.xml", O_RDONLY) = 6
                                           ^^^^^
[pid 29348] open("/usr/local/share/flightgear/Aircraft/_berg/j3cub.xml", O_RDONLY) = 19
                                                       ^^^^^

Huh??? OK, I confess. I had once copied some j3cub files to a new, local
directory "_berg" for a "Berg Aviatik" aircraft. Haven't renamed them there
and not kept them up-to-date either.

But why does fgfs pick up j3cub files from anywhere else than the j3cub
directory? It seriously searches for them in $FG_ROOT/Aircraft/747/?
Why? (Except to entertain me several hours long with debugging challenges. ;-)

m.

_______________________________________________
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel

Reply via email to