[Flightgear-devel] properties problem
Hi, The latest FlightGear from CVS gives me a core after startup. I traced it back to SimGear/simgear/misc/props.hxx line 730: Process 14190 (fgfs) stopped on signal SIGSEGV: Segmentation violation (default) at [SGPropertyNode::getAttribute(SGPropertyNode::Attribute) const:730 +0x10,0x103b2110] 730 bool getAttribute (Attribute attr) const { return ((_attr attr) != 0); } I have no idea why this happens. Does anybody else have any idea? Erik ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] properties problem
Julian Foad wrote: Erik Hofman wrote: The latest FlightGear from CVS gives me a core after startup. I traced it back to SimGear/simgear/misc/props.hxx line 730: Process 14190 (fgfs) stopped on signal SIGSEGV: Segmentation violation (default) at [SGPropertyNode::getAttribute(SGPropertyNode::Attribute) const:730 +0x10,0x103b2110] 730 bool getAttribute (Attribute attr) const { return ((_attr attr) != 0); } I have no idea why this happens. Does anybody else have any idea? I think you need to look higher up in the call stack: perhaps the object pointer on which this method is called was invalid. You are right, I forgot to mention: I tracked the probelm down to FlightGear/src/Maim/main.cxx SGTime *t = new SGTime( longitude-getDoubleValue() * SGD_DEGREES_TO_RADIANS, latitude-getDoubleValue() * SGD_DEGREES_TO_RADIANS, zone.str() ); Tests show that both longitude and latitude are false ... Hope this helps some more. Erik I'm lost at this one :( ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] properties problem
By false you mean they are null, I assume. Well, latitude and longitude are created a few lines further up by: // Any time after globals is created we are ready to use the // property system static const SGPropertyNode *longitude = fgGetNode(/position/longitude-deg, true); static const SGPropertyNode *latitude = fgGetNode(/position/latitude-deg, true); So these must be failing. There should probably be a check for null pointers there. - Julian Erik Hofman wrote: Julian Foad wrote: Erik Hofman wrote: The latest FlightGear from CVS gives me a core after startup. I traced it back to SimGear/simgear/misc/props.hxx line 730: Process 14190 (fgfs) stopped on signal SIGSEGV: Segmentation violation (default) at [SGPropertyNode::getAttribute(SGPropertyNode::Attribute) const:730 +0x10,0x103b2110] 730 bool getAttribute (Attribute attr) const { return ((_attr attr) != 0); } I have no idea why this happens. Does anybody else have any idea? I think you need to look higher up in the call stack: perhaps the object pointer on which this method is called was invalid. You are right, I forgot to mention: I tracked the probelm down to FlightGear/src/Maim/main.cxx SGTime *t = new SGTime( longitude-getDoubleValue() * SGD_DEGREES_TO_RADIANS, latitude-getDoubleValue() * SGD_DEGREES_TO_RADIANS, zone.str() ); Tests show that both longitude and latitude are false ... Hope this helps some more. Erik I'm lost at this one :( ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] Properties problem
Hi, Since a few days I have the following error message, and I can't find why ??!? /home/erik/fgfs/include/simgear/misc/props.hxx, line 837: error(1377): function SGPropertyNode::tie(const SGRawValueint , int) has already been declared bool tie (const SGRawValueint rawValue, bool useDefault = true); ^ /home/erik/fgfs/include/simgear/misc/props.hxx, line 988: error(1377): function SGPropertyNode::tie(const std::string , const SGRawValueint , int) has already been declared bool tie (const string relative_path, const SGRawValueint rawValue, ^ ../../src/Main/fg_props.hxx, line 468: error(1220): function fgTie has already been defined fgTie (const string name, int *pointer, bool useDefault = true) Does anybody have any idea why this happens? Erik ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel