Ron Lange wrote:
Hi Gerhard,
certainly I examine the variables, as mentioned the last created
thread try to access the properties, but the static property pointers
don't point to valid memory regions. The 'vel' property node is just
the first invalid, where the invalid access occured. The other
Hi Gerhard,
certainly I examine the variables, as mentioned the last created thread
try to access the properties, but the static property pointers don't
point to valid memory regions. The 'vel' property node is just the first
invalid, where the invalid access occured. The other two property
On Fri, Feb 11, 2005 at 04:14:15PM +0100, Ron Lange wrote:
double v = vel-getDoubleValue(); = segfault
Can you check vel in the debugger? Just set a breakpoint one line above
and enter ``print vel'' (in gdb).
Cheers
-Gerhard
--
Gerhard Wesp o o Tel.: +41 (0) 43
sorry, not the *commandline* below causes fg to break but similar
.fgfsrc file...
fgfs --airport=EDHI --aircraft=bo105 --enable-game-mode
#
Again, only a present .fgfsrc with similar content causes a segfault,
the commandline let
On Fri, 11 Feb 2005 16:14:15 +0100
Ron Lange wrote:
sorry, not the *commandline* below causes fg to break but similar
.fgfsrc file...
fgfs --airport=EDHI --aircraft=bo105 --enable-game-mode
#
Again, only a present
Jorge Van Hemelryck wrote:
Could you make sure that there is only one option per line in the
.fgfsrc file ? It looks like the parser is trying to set the airport
from the string EDHI --aircraft=bo105 --enable-game-mode...
Aaah, your comment reminds me that the parser is unable to parse
Hm...hmmm...since putting one flag per line in .fgfsrc wasn't satisfying
(not starting from EDHI nor with the bo-105...) I put all flags in one
row. Then everything goes as desired but the game mode...after adding
enabel-game-mode the segfault appeared.
Regards
Ron
Martin Spott schrieb:
Jorge
