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)]
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
-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
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
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
