> > On Monday 19 December 2005 21:26, Alex Romosan wrote:
> >> > The Interface is deleted and a new one is created.
> >> > That is a bit crude, but it works ...
> >>
> >> it doesn't work anymore though:
> >>
> >> Program received signal SIGSEGV, Segmentation fault.
> >> [Switching to Thread -1223874848 (LWP 22155)]
> >> 0x00000019 in ~logstream (this=0xbd3d3e8) at logstream.hxx:237
> >> 237 {
> > It's hard to help for me either since I cannot preproduce ATM.
> >
> it's happened with all the jsb aircraft i've tried so far (including
> the F80 dave culp just announced). i noticed this at sfo but i just
> tried a few random airports and the same thing happens. it does not
> happen with yasim planes. again, my jsb fdm has the carrier patch
> applied.
>
IIRC a destructor can't call virtual methods, so if the interface
needs to do some kind of cleanup it can only be something pertaining
to this instance and using just the compile-time resolved calls.
I haven't looked at the code you cite above so this might be irrelevant
there, but I am a bit suspicious because of the name "FGInterface" that
hints at an abstract class.
Sorry I am overloaded with non-fgfs tasks right now --- I haven't even
pulled the last week's CVS updates and haven't reviewed them :-( ---
but maybe sharing this piece of info is better than doing nothing at all.
V.
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d
