Re: [Flightgear-devel] segfault on mini-panels

2002-03-21 Thread David Megginson
Jim Wilson writes: > Is there a method for rotating through a list in the xml? When I first set > that up there wasn't any...so it just does a swap from panel2/path to the > panel/path. Panel[2] might not be correct. Perhaps we should have a panel- > current-idx property that defines wh

Re: [Flightgear-devel] segfault on mini-panels

2002-03-21 Thread Jim Wilson
David Megginson <[EMAIL PROTECTED]> said: > Jim Wilson writes: > > > Here's a backtrace on this. > > I've just checked in some minor fixes to props.cxx in SimGear, and > swapping panels (with 's') in FlightGear is working again. Thanks. > > By the way, we need to get rid of the panel_2 prope

Re: [Flightgear-devel] segfault on mini-panels

2002-03-21 Thread David Megginson
Jim Wilson writes: > Here's a backtrace on this. I've just checked in some minor fixes to props.cxx in SimGear, and swapping panels (with 's') in FlightGear is working again. Thanks. By the way, we need to get rid of the panel_2 property; instead, we should have panel[0], panel[1], panel[2],

Re: [Flightgear-devel] segfault on mini-panels

2002-03-20 Thread Jim Wilson
Here's a backtrace on this. Best, Jim #0 0x82ddfba in SGPropertyNode::clear_value (this=0x9747f90) at props.cxx:464 464 delete _value.string_val; #1 0x82de8e0 in SGPropertyNode::~SGPropertyNode (this=0x9747f90, __in_chrg=3) at props.cxx:672 #2 0x806c0e0 in FGComparisonCondition::

Re: [Flightgear-devel] segfault on mini-panels

2002-03-20 Thread Alex Perry
> When I try to switch to a mini-panel, I always get a segfault (I've > tested in c172 and c310). Is anyone else seeing this? I'm using a > clean CVS build from yesterday (ie. prior to David's property code > changes) with no command-line options. Thanks It was working for me a couple of days

RE: [Flightgear-devel] segfault on mini-panels

2002-03-19 Thread Norman Vine
Cameron Moore writes: > >When I try to switch to a mini-panel, I always get a segfault (I've >tested in c172 and c310). Is anyone else seeing this? I'm using a >clean CVS build from yesterday (ie. prior to David's property code >changes) with no command-line options. Yep :-( I started gettin