Norman Vine writes:
Hopefully once we get 'reset' working again developers will test 'reset'
before submitting their changes in the future so we don't repeat this
quagmire
It's a little more complicated than that. The original reset was a
simple kludge that worked fine for a simple
David Megginson writes:
Norman Vine writes:
Hopefully once we get 'reset' working again developers will test 'reset'
before submitting their changes in the future so we don't repeat this
quagmire
It's a little more complicated than that. The original reset was a
simple kludge that
David Megginson [EMAIL PROTECTED] said:
Curt has mentioned that there are ordering dependencies, especially
around rendering, that we have to be careful not to break. We should
be able to get those automatically, as long as we add the subsystems
to the vector in the right order.
The
Curtis L. Olson writes:
David, I'm looking for help on this one since it's seems to be very
much wrapped up in the property system and environment manager and
cloud layers.
This problem seems to be very complicated.
Agreed. I've managed to patch things up in my local copy so that it
David Megginson writes:
Curtis L. Olson writes:
David, I'm looking for help on this one since it's seems to be very
much wrapped up in the property system and environment manager and
cloud layers.
This problem seems to be very complicated.
Agreed.
Remember that reset has
always
Norman Vine [EMAIL PROTECTED] said:
Hopefully once we get 'reset' working again developers will test 'reset'
before submitting their changes in the future so we don't repeat this
quagmire
Maybe that should be part of a minimum test before something is commited to cvs?
Actually my most
Jim Wilson writes:
Curtis L. Olson [EMAIL PROTECTED] said:
Has anyone tried to debug the Reset menu crash?
Yes, right after the cloud layer changes went in it started. David knows
about it. Comment out the cloud layer config in preferences.xml and the
problem goes away (but you have
Curtis L. Olson writes:
Jim Wilson writes:
Curtis L. Olson [EMAIL PROTECTED] said:
Has anyone tried to debug the Reset menu crash?
Yes, right after the cloud layer changes went in it started. David knows
about it. Comment out the cloud layer config in preferences.xml and the
Jim Wilson writes:
Yes, right after the cloud layer changes went in it started. David
knows about it. Comment out the cloud layer config in
preferences.xml and the problem goes away (but you have no clouds).
It appears there's something that isn't getting cleaned up in the
simgear code.
Curtis L. Olson [EMAIL PROTECTED] said:
At the start of the program we save a copy of the property tree. As
part of restoring the initial state we copy back this saved property
tree to the current/master property tree. Because of callbacks
(functions tied to property reads and writes)
Curtis L. Olson [EMAIL PROTECTED] said:
Has anyone tried to debug the Reset menu crash?
Yes, right after the cloud layer changes went in it started. David knows
about it. Comment out the cloud layer config in preferences.xml and the
problem goes away (but you have no clouds). It appears
Curtis L. Olson writes:
Has anyone tried to debug the Reset menu crash?
Yep, but no joy.
This is a bug we shouldn't let sit around very long. The longer it
sits, the harder it will be to track down.
FWIW:
It is curious that 'goto airport' seems to still work
Norman
Curtis L. Olson wrote:
Has anyone tried to debug the Reset menu crash? I've been looking
at it for an hour and am just going in circles. Half the time I get a
segfault with no backtrace ...
I don't remember what a malloc segfault exactly
means, but I seem to recall that it probably means
13 matches
Mail list logo
