Re: [Flightgear-devel] segfault in SimGear code
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 two property nodes within this scope are invalid, too. Can anyone also cause this segfault by using with an .fgfsrc containing just one line --airport=EDHI --aircraft=bo105 --enable-game-mode Ron, Definitely you should put one option per line. The parser simply wasn't designed to accept input the way you have it. Regards, Curt. -- Curtis Olsonhttp://www.flightgear.org/~curt HumanFIRST Program http://www.humanfirst.umn.edu/ FlightGear Project http://www.flightgear.org Unique text:2f585eeea02e2c79d7b1d8c4963bae2d ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] segfault in SimGear code
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 nodes within this scope are invalid, too. Can anyone also cause this segfault by using with an .fgfsrc containing just one line --airport=EDHI --aircraft=bo105 --enable-game-mode ? Regards Ron Gerhard Wesp schrieb: 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 ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] segfault in SimGear code
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 5347636 Bachtobelstrasse 56 | http://www.cosy.sbg.ac.at/~gwesp/ CH-8045 Zuerich \_/ See homepage for email address! ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] segfault in SimGear code
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 fg regulary start.
Second hint: following message appeared twice:
Failed to find runway 28R at airport EDHI --aircraft=bo105
--enable-game-mode
Failed to find a good runway for EDHI --aircraft=bo105 --enable-game-mode
gdb session points on
Autopilot/xmlauto.cxx:804 ff
static void update_helper( double dt ) {
// Estimate speed in 5,10 seconds
static SGPropertyNode *vel = fgGetNode( /velocities/airspeed-kt,
true );
static SGPropertyNode *lookahead5
= fgGetNode( /autopilot/internal/lookahead-5-sec-airspeed-kt,
true );
static SGPropertyNode *lookahead10
= fgGetNode( /autopilot/internal/lookahead-10-sec-airspeed-kt,
true );
static double average = 0.0; // average/filtered prediction
static double v_last = 0.0; // last velocity
double v = vel-getDoubleValue(); = segfault
obvisously the last thread has no longer access to valid property nodes.
Regards
Ron
___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] segfault in SimGear code
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 .fgfsrc with similar content causes a segfault, the commandline let fg regulary start. Second hint: following message appeared twice: Failed to find runway 28R at airport EDHI --aircraft=bo105 --enable-game-mode Failed to find a good runway for EDHI --aircraft=bo105 --enable-game-mode 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... -- Jorge Van Hemelryck ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] segfault in SimGear code
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 multiple options per line from the ~/.fgfsrc file - although I always had the impression that the parser simply ignores the following flags (it still would be nice if the parser could cope with multiple flags), Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] segfault in SimGear code
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 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 multiple options per line from the ~/.fgfsrc file - although I always had the impression that the parser simply ignores the following flags (it still would be nice if the parser could cope with multiple flags), Martin. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
