I'm facing a strange bug in fgfs, that I couldn't fix yet: If I connect to
fgfs via telnet and enter "cd .." at the root level, fgfs segfaults.
I tracked this down and found that simgear/misc/props.cxx:273 does detect
this correctly and throws an exception ("Attempt to move past root with '..'").
So FlightGear/src/Network/props.cxx should catch this (and other exceptions)
and output an error message, rather than letting fgfs abort. Unfortunately,
I failed to catch these exceptions. Why are exceptions thrown in SimGear
not catchable in FlightGear? Am I missing something?
Also, I don't get fgfs compiled with debug symbols, although I configure
with "--enable-debug" and get "Debug messages: yes" in the "Configure summary".
Is there something else to consider? (apart from adding the -g flag
manually ;-) configure --help doesn't say =anything= about debugging.
m.
PS: I know that fgfs is in a kind of freeze wrt new features. I sent
the telnet patch today, because it was ready =before= the freeze
was announced. :-]
_______________________________________________
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
