Re: [Flightgear-devel] Re: Sim Reset
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Vassilii Khachaturov schrieb: > 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. Not knowing if it helps (I don't even know about what part of the code you are talking about): Virtual functions can be avoided in many cases by using the so called Barton-Nackman trick (http://en.wikipedia.org/wiki/Barton-Nackman)... CU, Christian -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (MingW32) iD8DBQFDqFJFlhWtxOxWNFcRAr5eAJ42G38BOCWzN5QysINniU+2Tfp9sQCgt81Q 12s6Yq3RH93GlvlN3FUmcyA= =iW5n -END PGP SIGNATURE- ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: Sim Reset
Alex Romosan wrote: Alex Romosan <[EMAIL PROTECTED]> writes: + delete Atmosphere; Atmosphere=0; I know there's no real styleguide for FlightGear. But please let's stick to the one command per line rule. Lines are not that expensive after all :) And I think it's even more obvious, when you can look if only every odd line is a delete. delete Atmosphere; Atmosphere=0; delete FCS; FCS=0; delete Propulsion; Propulsion=0; Nine ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: Sim Reset
> > 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)] > >> 0x0019 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
Re: [Flightgear-devel] Re: Sim Reset
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)] > 0x0019 in ~logstream (this=0xbd3d3e8) at logstream.hxx:237 > 237 { It's hard to help for me either since I cannot preproduce ATM. Which aircraft, airport? Commandline flags? Your ~/.fgfs*? Greetings Mathias -- Mathias Fröhlich, email: [EMAIL PROTECTED] ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] Re: Sim Reset
> 0x0019 in ~logstream (this=0xbd3d3e8) at logstream.hxx:237 > 237 { > > (gdb) where > #0 0x0019 in ~logstream (this=0xbd3d3e8) at logstream.hxx:237 > #1 0x0812a812 in ~FGFDMExec (this=0xbd3d3e8) at FGFDMExec.cpp:173 > #2 0x08113095 in ~FGJSBsim (this=0xb4b39e0) at JSBSim.cxx:308 What on earth is logstream? Jon ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d