Re: [Flightgear-devel] Segfault from todays CVS
Hi, On Samstag 19 Februar 2005 20:01, Jon Stockill wrote: I've just had a thought presumably now the ground cache code has been added it would be possible to have a carrier with a ski jump for the harrier model? That opens up another interesting area of deck operations. Yes, I think it should be possible. Build up a configuration file for that carrier and include the object name of that ski jump 3d object in a solid tag. Then that object is used for ground intersection tests. Take a look into Data/AI/nimitz_demo.xml for an example. 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] Segfault from todays CVS
Good morning, (... at least in europe :) On Samstag 19 Februar 2005 14:59, Jon Stockill wrote: It turned out there was an ancient version of GLU hiding in /usr/local - which hadn't caused any problems until now - eliminating that solved the problem. Good. Thanks for the feedback anyway! Right... where's that aircraft carrier :-) :) See the more lenghtly announcement with the subject: YASim gears exactly following ground/Aircraft Carrier 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] Segfault from todays CVS
Vivian Meazza wrote: Mathias would need to reply definitively, but I think so. Just by chance I have been fiddling with a model of HMS Hermes with a ski-jump, but I was going to remove it, and restore it to her strike carrier days. I served aboard her in her last commission as a strike carrier. I just discovered a selection of 3views on aerospaceweb.org (not particularly high resolution, but possibly enough to work from). Including one on this page: http://www.aerospaceweb.org/aircraft/bomber/buccaneer/ :-) -- Jon Stockill [EMAIL PROTECTED] ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Segfault from todays CVS
Vivian Meazza wrote: I'm not sure that the Nimitz version in cvs has cats. If it has, then don't forget that the Seahawk has differential brakes, and no nosewheel steering. I have a more detailed version available here: ftp://ftp.abbeytheatre.dynu.com/fgfs/Nimitz/ Warning: it's still under development, and some of the textures are HUGE. Have any object names changed from the previous version? I found I droped straight through the deck, the hangar below, and only stopped when I hit the water. The model does look *VERY* nice though (even from the inside ;-)) -- Jon Stockill [EMAIL PROTECTED] ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] Segfault from todays CVS
Jon Stockill Vivian Meazza wrote: I'm not sure that the Nimitz version in cvs has cats. If it has, then don't forget that the Seahawk has differential brakes, and no nosewheel steering. I have a more detailed version available here: ftp://ftp.abbeytheatre.dynu.com/fgfs/Nimitz/ Warning: it's still under development, and some of the textures are HUGE. Have any object names changed from the previous version? I found I droped straight through the deck, the hangar below, and only stopped when I hit the water. The model does look *VERY* nice though (even from the inside ;-)) Yes, make sure that this is in your ...Data/AI/nimitz-demo.xml file: solidElevator-3-Deck/solid solidDeck/solid In place of whatever solid.../solid appears there now. That should fix it. Regards Vivian ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Segfault from todays CVS
Vivian Meazza wrote: Yes, make sure that this is in your ...Data/AI/nimitz-demo.xml file: solidElevator-3-Deck/solid solidDeck/solid In place of whatever solid.../solid appears there now. Ah, so I fell through the elevator then :-) That would explain the view of the hangar deck. -- Jon Stockill [EMAIL PROTECTED] ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] Segfault from todays CVS
Jon Stockill wrote: Vivian Meazza wrote: Yes, make sure that this is in your ...Data/AI/nimitz-demo.xml file: solidElevator-3-Deck/solid solidDeck/solid In place of whatever solid.../solid appears there now. Ah, so I fell through the elevator then :-) That would explain the view of the hangar deck. You weren't quite on the centre line then? :-) Otherwise, it works? Regards, Vivian ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] Segfault from todays CVS
From: Vivian Meazza Jon Stockill wrote: Vivian Meazza wrote: Yes, make sure that this is in your ...Data/AI/nimitz-demo.xml file: solidElevator-3-Deck/solid solidDeck/solid In place of whatever solid.../solid appears there now. Ah, so I fell through the elevator then That would explain the view of the hangar deck. You weren't quite on the centre line then? Otherwise, it works? Is it just me or has this conversation veered way off the original subject a long time ago? Somone may want to rename the topic as it looks like modelers and other non-programming developers could be interested in the discussion. :-) Best regards, Jim Wilson ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] Segfault from todays CVS
Jim Wilson wrote: From: Vivian Meazza Jon Stockill wrote: Vivian Meazza wrote: Yes, make sure that this is in your ...Data/AI/nimitz-demo.xml file: solidElevator-3-Deck/solid solidDeck/solid In place of whatever solid.../solid appears there now. Ah, so I fell through the elevator then That would explain the view of the hangar deck. You weren't quite on the centre line then? Otherwise, it works? Is it just me or has this conversation veered way off the original subject a long time ago? Somone may want to rename the topic as it looks like modelers and other non-programming developers could be interested in the discussion. :-) Has it ever! But some like to stick with the original thread, and some like to change. It's about done now either way. Regards, Vivian ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Segfault from todays CVS
Mathias Fröhlich wrote: Hi, On Freitag 18 Februar 2005 17:30, Frederic Bouvier wrote: Are you sure your runtime librairies ( that seems to be compiled with gcc-2.95.3 ) match your compiler ? That is my impression too. It turned out there was an ancient version of GLU hiding in /usr/local - which hadn't caused any problems until now - eliminating that solved the problem. Right... where's that aircraft carrier :-) -- Jon Stockill [EMAIL PROTECTED] ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] Segfault from todays CVS
Jon Stockill Mathias Fröhlich wrote: Hi, On Freitag 18 Februar 2005 17:30, Frederic Bouvier wrote: Are you sure your runtime librairies ( that seems to be compiled with gcc-2.95.3 ) match your compiler ? That is my impression too. It turned out there was an ancient version of GLU hiding in /usr/local - which hadn't caused any problems until now - eliminating that solved the problem. Right... where's that aircraft carrier :-) Let us know how you get on. Melchior claims the first successful Seafire landing. Regards, Vivian ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Segfault from todays CVS
Vivian Meazza wrote: Let us know how you get on. Melchior claims the first successful Seafire landing. Took off from KSFO, and nailed the seahawk to the deck on the first try, then couldn't work out how to get the thing onto the cat to launch. That secondary ASI comes in rather handy :-) -- Jon Stockill [EMAIL PROTECTED] ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] Segfault from todays CVS
Jon Stockill wrote: Vivian Meazza wrote: Let us know how you get on. Melchior claims the first successful Seafire landing. Took off from KSFO, and nailed the seahawk to the deck on the first try, Well done. then couldn't work out how to get the thing onto the cat to launch. I'm not sure that the Nimitz version in cvs has cats. If it has, then don't forget that the Seahawk has differential brakes, and no nosewheel steering. I have a more detailed version available here: ftp://ftp.abbeytheatre.dynu.com/fgfs/Nimitz/ Warning: it's still under development, and some of the textures are HUGE. That secondary ASI comes in rather handy :-) It was called the Deck Landing ASI :-) IIRC. Judging by some reports, the Seahawk was probably one of the easiest, if not the easiest, jet to deck land before the current era of auto-land etc. Regards, Vivian ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Segfault from todays CVS
Vivian Meazza wrote: Well done. It was easier than I expected. ftp://ftp.abbeytheatre.dynu.com/fgfs/Nimitz/ Warning: it's still under development, and some of the textures are HUGE. I'll grab that and have a go tomorrow. That secondary ASI comes in rather handy :-) It was called the Deck Landing ASI :-) IIRC. Judging by some reports, the Seahawk was probably one of the easiest, if not the easiest, jet to deck land before the current era of auto-land etc. It's certainly easier than I expected - the approach speed is nice and low, and there's acres of deck to aim for - obviously you want to hit the bit with the wires, but at least you ca see what you should be aiming for. I've just had a thought presumably now the ground cache code has been added it would be possible to have a carrier with a ski jump for the harrier model? That opens up another interesting area of deck operations. -- Jon Stockill [EMAIL PROTECTED] ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] Segfault from todays CVS
Jon Stockill Vivian Meazza wrote: Well done. It was easier than I expected. ftp://ftp.abbeytheatre.dynu.com/fgfs/Nimitz/ Warning: it's still under development, and some of the textures are HUGE. I'll grab that and have a go tomorrow. That secondary ASI comes in rather handy :-) It was called the Deck Landing ASI :-) IIRC. Judging by some reports, the Seahawk was probably one of the easiest, if not the easiest, jet to deck land before the current era of auto-land etc. It's certainly easier than I expected - the approach speed is nice and low, and there's acres of deck to aim for - obviously you want to hit the bit with the wires, but at least you ca see what you should be aiming for. I've just had a thought presumably now the ground cache code has been added it would be possible to have a carrier with a ski jump for the harrier model? That opens up another interesting area of deck operations. Mathias would need to reply definitively, but I think so. Just by chance I have been fiddling with a model of HMS Hermes with a ski-jump, but I was going to remove it, and restore it to her strike carrier days. I served aboard her in her last commission as a strike carrier. Regards, Vivian ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] Segfault from todays CVS
Jon Stockill wrote Vivian Meazza wrote: Well done. It was easier than I expected. ftp://ftp.abbeytheatre.dynu.com/fgfs/Nimitz/ Warning: it's still under development, and some of the textures are HUGE. I'll grab that and have a go tomorrow. If you take it all, you might also like the improved FLOLS at: ftp://ftp.abbeytheatre.dynu.com/fgfs/flols-20050208 Regards, Vivian ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Segfault from todays CVS
Jon,
I cannot reproduce this.
It just works for me with a plain cvs checkout
using that scenry tile from Scenery-0.9.8.
On Freitag 18 Februar 2005 01:24, Jon Stockill wrote:
(gdb) bt
#0 0x0ce8b760 in ?? ()
#1 0x40142974 in __dynamic_cast (from=0xce8b760,
to=0x8548f9c typeinfo for ssgBase, require_public=139557448,
address=0x0, sub=0xbfffee80, subptr=0xbfffee8b)
at ../../gcc-2.95.3/gcc/cp/tinfo2.cc:282
#2 0x081241cc in FGGroundCache::get_agl ()
From that backtrace:
There is exactly one dynamic_cast in this function.
In theory it should never happen that the argument to that dynamic_cast is
zero.
Since I cannot reproduce it myself, can you help me?
Could you please apply the attached patch and tell me of some of thouse new
cerr output lines triggers?
Greetings
Mathias
--
Mathias Fröhlich, email: [EMAIL PROTECTED]
Index: src/FDM/groundcache.cxx
===
RCS file: /var/cvs/FlightGear-0.9/source/src/FDM/groundcache.cxx,v
retrieving revision 1.4
diff -u -r1.4 groundcache.cxx
--- src/FDM/groundcache.cxx 17 Feb 2005 10:26:14 - 1.4
+++ src/FDM/groundcache.cxx 18 Feb 2005 15:01:29 -
@@ -114,7 +114,7 @@
gp-type = FGInterface::Forest;
}
}
-
+
return gp;
}
@@ -153,6 +153,18 @@
// Check for magic texture names object names and such ...
vtxa-setUserData( extractGroundProperty( l ) );
vtxa-setCullFace( l-getCullFace() );
+
+ ssgBase *gpb = vtxa-getUserData();
+ // Assertation???
+ if ( !gpb ) {
+cerr Newly created cache leaf without userdata! endl;
+ }
+ GroundProperty *gp = dynamic_castGroundProperty*(gpb);
+ // Assertation???
+ if ( !gp ) {
+cerr Newly created cache leaf where userdata is not a Ground property! endl;
+ }
+
// Finally append to cache.
cache_root.addKid((ssgEntity*)vtxa);
}
@@ -509,10 +521,18 @@
// AGL computations are done with triangle/surface leafs.
if (va-getPrimitiveType() != GL_TRIANGLES)
continue;
-GroundProperty *gp = dynamic_castGroundProperty*(va-getUserData());
+ssgBase *gpb = va-getUserData();
// Assertation???
-if ( !gp )
+if ( !gpb ) {
+ cerr Found cache leaf without userdata! endl;
+ continue;
+}
+GroundProperty *gp = dynamic_castGroundProperty*(gpb);
+// Assertation???
+if ( !gp ) {
+ cerr Found cache leaf where userdata is not a GroundProperty! endl;
continue;
+}
int nt = va-getNumTriangles();
for (int i=0; i nt; ++i) {
___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Segfault from todays CVS
Quoting Frederic Bouvier: Quoting Mathias Fröhlich : Jon, I cannot reproduce this. It just works for me with a plain cvs checkout using that scenry tile from Scenery-0.9.8. On Freitag 18 Februar 2005 01:24, Jon Stockill wrote: (gdb) bt #0 0x0ce8b760 in ?? () #1 0x40142974 in __dynamic_cast (from=0xce8b760, to=0x8548f9c typeinfo for ssgBase, require_public=139557448, address=0x0, sub=0xbfffee80, subptr=0xbfffee8b) at ../../gcc-2.95.3/gcc/cp/tinfo2.cc:282 #2 0x081241cc in FGGroundCache::get_agl () From that backtrace: There is exactly one dynamic_cast in this function. In theory it should never happen that the argument to that dynamic_cast is zero. Since I cannot reproduce it myself, can you help me? Could you please apply the attached patch and tell me of some of thouse new cerr output lines triggers? I don't know if it is true for gcc, but with MSVC, rtti needs to be activated with a specific compile-time option otherwise the result is unpredictable. And Jon seems to use an old version of gcc : 2.95.3 -Fred ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Segfault from todays CVS
Quoting Mathias Fröhlich : Jon, I cannot reproduce this. It just works for me with a plain cvs checkout using that scenry tile from Scenery-0.9.8. On Freitag 18 Februar 2005 01:24, Jon Stockill wrote: (gdb) bt #0 0x0ce8b760 in ?? () #1 0x40142974 in __dynamic_cast (from=0xce8b760, to=0x8548f9c typeinfo for ssgBase, require_public=139557448, address=0x0, sub=0xbfffee80, subptr=0xbfffee8b) at ../../gcc-2.95.3/gcc/cp/tinfo2.cc:282 #2 0x081241cc in FGGroundCache::get_agl () From that backtrace: There is exactly one dynamic_cast in this function. In theory it should never happen that the argument to that dynamic_cast is zero. Since I cannot reproduce it myself, can you help me? Could you please apply the attached patch and tell me of some of thouse new cerr output lines triggers? I don't know if it is true for gcc, but with MSVC, rtti needs to be activated with a specific compile-time option otherwise the result is unpredictable. -Fred ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Segfault from todays CVS
Hi, On Freitag 18 Februar 2005 16:08, Frederic Bouvier wrote: I don't know if it is true for gcc, but with MSVC, rtti needs to be activated with a specific compile-time option otherwise the result is unpredictable. I see, this is the first usage of rtti in flightgear. But all those dynamic_casts here are more a 'be paranoid and double check to be really shure' than real application of rtti. So if this turns out to be the real problem we can remove them. gcc normally enables rtti by default. At least gcc 3.4.2 and gcc-4presomething I have installed on my fedora core 3. The gcc-2.95.3 manpage does not tell anything about that. But from the backtrace and the prehistoric gcc-2.95.3 sources I would think that the input pointer was zero which I cannot imagine to happen ATM. Hmm. 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] Segfault from todays CVS
Mathias Fröhlich wrote: Hi, On Freitag 18 Februar 2005 16:08, Frederic Bouvier wrote: I don't know if it is true for gcc, but with MSVC, rtti needs to be activated with a specific compile-time option otherwise the result is unpredictable. I see, this is the first usage of rtti in flightgear. But all those dynamic_casts here are more a 'be paranoid and double check to be really shure' than real application of rtti. So if this turns out to be the real problem we can remove them. gcc normally enables rtti by default. At least gcc 3.4.2 and gcc-4presomething I have installed on my fedora core 3. The gcc-2.95.3 manpage does not tell anything about that. But from the backtrace and the prehistoric gcc-2.95.3 sources I would think that the input pointer was zero which I cannot imagine to happen ATM. Hmm. It's actually GCC 3.3.4. I've just cleared everything out and started building it from scratch - I'll let you know if there's still a problem. -- Jon Stockill [EMAIL PROTECTED] ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Segfault from todays CVS
Mathias Fröhlich wrote: From that backtrace: There is exactly one dynamic_cast in this function. In theory it should never happen that the argument to that dynamic_cast is zero. Since I cannot reproduce it myself, can you help me? Could you please apply the attached patch and tell me of some of thouse new cerr output lines triggers? After a rebuild (with your patch): (gdb) run --aircraft=hunter --airport=RCSS Starting program: /usr/bin/fgfs --aircraft=hunter --airport=RCSS [Thread debugging using libthread_db enabled] [New Thread 16384 (LWP 18031)] Failed to find runway 28R at airport RCSS [New Thread 32769 (LWP 18033)] [New Thread 16386 (LWP 18034)] [New Thread 32771 (LWP 18035)] [New Thread 49156 (LWP 18036)] Altitude = 18 Temp at alt (C) = 12 Temp sea level (C) = 12.0348 Altitude = 18 Dewpoint at alt (C) = 10 Dewpoint at sea level (C) = 10.0036 Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 16384 (LWP 18031)] 0x0cdf665b in ?? () (gdb) bt #0 0x0cdf665b in ?? () #1 0x in ?? () #2 0x40142974 in __dynamic_cast (from=0xcdf6658, to=0x854ca9c typeinfo for ssgBase, require_public=139573480, address=0x0, sub=0x405d49d0 main_arena+16, subptr=0x38) at ../../gcc-2.95.3/gcc/cp/tinfo2.cc:282 #3 0x0812233d in FGGroundCache::addAndFlattenLeaf (this=0xb060818, ty=4, l=0x5153f0a8, ia=0xcdf6658, xform=0xb0f0) at groundcache.cxx:159 #4 0x0812281f in FGGroundCache::putSurfaceLeafIntoCache (this=0xb060818, sp=0xb320, xform=0xb0f0, sphIsec=true, down=0xb2c0, l=0x5153f0a8) at groundcache.cxx:260 #5 0x08122d5a in FGGroundCache::cache_fill (this=0xb060818, branch=0x513ffc78, xform=0xb0f0, sp=0xb320, down=0xb2c0, wsp=0xb2d0) at groundcache.cxx:337 #6 0x08122cf7 in FGGroundCache::cache_fill (this=0xb060818, branch=0xcc15720, xform=0xb0f0, sp=0xb320, down=0xb2c0, wsp=0xb2d0) at groundcache.cxx:323 #7 0x08122cf7 in FGGroundCache::cache_fill (this=0xb060818, branch=0xcbd7be8, xform=0xb0f0, sp=0xb320, down=0xb2c0, wsp=0xb2d0) at groundcache.cxx:323 #8 0x08122cf7 in FGGroundCache::cache_fill (this=0xb05c818, branch=0xc3b9b70, xform=0xb0f0, sp=0xb320, down=0xb2c0, wsp=0xb2d0) at groundcache.cxx:323 #9 0x08122cf7 in FGGroundCache::cache_fill (this=0xb05c818, branch=0xcbb2a10, xform=0xb0f0, sp=0xb320, down=0xb2c0, wsp=0xb2d0) at groundcache.cxx:323 #10 0x08122cf7 in FGGroundCache::cache_fill (this=0xb05c818, branch=0x8ff0118, xform=0xb280, sp=0xb320, down=0xb2c0, wsp=0xb2d0) at groundcache.cxx:323 #11 0x08122cf7 in FGGroundCache::cache_fill (this=0xb05c818, branch=0x8ff0090, xform=0xb280, sp=0xb320, down=0xb2c0, wsp=0xb2d0) ---Type return to continue, or q return to quit--- at groundcache.cxx:323 #12 0x08123075 in FGGroundCache::prepare_ground_cache (this=0xb05c818, ref_time=0, pt=0xb3e0, rad=10.407214164733887) at groundcache.cxx:403 #13 0x08121068 in FGInterface::prepare_ground_cache_m (this=0xb05c178, ref_time=0, pt=0xb3e0, rad=10.407214164733887) at flight.cxx:796 #14 0x081b06c2 in YASim::update (this=0xb05c178, dt=0.81665) at YASim.cxx:202 #15 0x08051d6a in fgUpdateTimeDepCalcs () at main.cxx:167 #16 0x08052759 in fgMainLoop () at main.cxx:431 #17 0x08086232 in GLUTidle () at fg_os.cxx:114 #18 0x4009b1c0 in idleWait () from /usr/local/lib/libglut.so.3 #19 0x4009b8bb in glutMainLoop () from /usr/local/lib/libglut.so.3 #20 0x08054d1d in fgMainInit (argc=3, argv=0xb7e4) at main.cxx:958 #21 0x08051746 in main (argc=3, argv=0xb7e4) at bootstrap.cxx:192 I can't explain the gcc version reported there though, because: gcc -v Reading specs from /usr/lib/gcc-lib/i486-slackware-linux/3.3.4/specs Configured with: ../gcc-3.3.4/configure --prefix=/usr --enable-shared --enable-threads=posix --enable-__cxa_atexit --disable-checking --with-gnu-ld --verbose --target=i486-slackware-linux --host=i486-slackware-linux Thread model: posix gcc version 3.3.4 -- Jon Stockill [EMAIL PROTECTED] ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Segfault from todays CVS
Quoting Jon Stockill : Mathias Fröhlich wrote: From that backtrace: There is exactly one dynamic_cast in this function. In theory it should never happen that the argument to that dynamic_cast is zero. Since I cannot reproduce it myself, can you help me? Could you please apply the attached patch and tell me of some of thouse new cerr output lines triggers? After a rebuild (with your patch): (gdb) run --aircraft=hunter --airport=RCSS Starting program: /usr/bin/fgfs --aircraft=hunter --airport=RCSS [Thread debugging using libthread_db enabled] [New Thread 16384 (LWP 18031)] Failed to find runway 28R at airport RCSS [New Thread 32769 (LWP 18033)] [New Thread 16386 (LWP 18034)] [New Thread 32771 (LWP 18035)] [New Thread 49156 (LWP 18036)] Altitude = 18 Temp at alt (C) = 12 Temp sea level (C) = 12.0348 Altitude = 18 Dewpoint at alt (C) = 10 Dewpoint at sea level (C) = 10.0036 Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 16384 (LWP 18031)] 0x0cdf665b in ?? () (gdb) bt #0 0x0cdf665b in ?? () #1 0x in ?? () #2 0x40142974 in __dynamic_cast (from=0xcdf6658, to=0x854ca9c typeinfo for ssgBase, require_public=139573480, address=0x0, sub=0x405d49d0 main_arena+16, subptr=0x38) at ../../gcc-2.95.3/gcc/cp/tinfo2.cc:282 #3 0x0812233d in FGGroundCache::addAndFlattenLeaf (this=0xb060818, ty=4, l=0x5153f0a8, ia=0xcdf6658, xform=0xb0f0) at groundcache.cxx:159 #4 0x0812281f in FGGroundCache::putSurfaceLeafIntoCache (this=0xb060818, sp=0xb320, xform=0xb0f0, sphIsec=true, down=0xb2c0, l=0x5153f0a8) at groundcache.cxx:260 #5 0x08122d5a in FGGroundCache::cache_fill (this=0xb060818, branch=0x513ffc78, xform=0xb0f0, sp=0xb320, down=0xb2c0, wsp=0xb2d0) at groundcache.cxx:337 #6 0x08122cf7 in FGGroundCache::cache_fill (this=0xb060818, branch=0xcc15720, xform=0xb0f0, sp=0xb320, down=0xb2c0, wsp=0xb2d0) at groundcache.cxx:323 #7 0x08122cf7 in FGGroundCache::cache_fill (this=0xb060818, branch=0xcbd7be8, xform=0xb0f0, sp=0xb320, down=0xb2c0, wsp=0xb2d0) at groundcache.cxx:323 #8 0x08122cf7 in FGGroundCache::cache_fill (this=0xb05c818, branch=0xc3b9b70, xform=0xb0f0, sp=0xb320, down=0xb2c0, wsp=0xb2d0) at groundcache.cxx:323 #9 0x08122cf7 in FGGroundCache::cache_fill (this=0xb05c818, branch=0xcbb2a10, xform=0xb0f0, sp=0xb320, down=0xb2c0, wsp=0xb2d0) at groundcache.cxx:323 #10 0x08122cf7 in FGGroundCache::cache_fill (this=0xb05c818, branch=0x8ff0118, xform=0xb280, sp=0xb320, down=0xb2c0, wsp=0xb2d0) at groundcache.cxx:323 #11 0x08122cf7 in FGGroundCache::cache_fill (this=0xb05c818, branch=0x8ff0090, xform=0xb280, sp=0xb320, down=0xb2c0, wsp=0xb2d0) ---Type return to continue, or q return to quit--- at groundcache.cxx:323 #12 0x08123075 in FGGroundCache::prepare_ground_cache (this=0xb05c818, ref_time=0, pt=0xb3e0, rad=10.407214164733887) at groundcache.cxx:403 #13 0x08121068 in FGInterface::prepare_ground_cache_m (this=0xb05c178, ref_time=0, pt=0xb3e0, rad=10.407214164733887) at flight.cxx:796 #14 0x081b06c2 in YASim::update (this=0xb05c178, dt=0.81665) at YASim.cxx:202 #15 0x08051d6a in fgUpdateTimeDepCalcs () at main.cxx:167 #16 0x08052759 in fgMainLoop () at main.cxx:431 #17 0x08086232 in GLUTidle () at fg_os.cxx:114 #18 0x4009b1c0 in idleWait () from /usr/local/lib/libglut.so.3 #19 0x4009b8bb in glutMainLoop () from /usr/local/lib/libglut.so.3 #20 0x08054d1d in fgMainInit (argc=3, argv=0xb7e4) at main.cxx:958 #21 0x08051746 in main (argc=3, argv=0xb7e4) at bootstrap.cxx:192 I can't explain the gcc version reported there though, because: gcc -v Reading specs from /usr/lib/gcc-lib/i486-slackware-linux/3.3.4/specs Configured with: ../gcc-3.3.4/configure --prefix=/usr --enable-shared --enable-threads=posix --enable-__cxa_atexit --disable-checking --with-gnu-ld --verbose --target=i486-slackware-linux --host=i486-slackware-linux Thread model: posix gcc version 3.3.4 Are you sure your runtime librairies ( that seems to be compiled with gcc-2.95.3 ) match your compiler ? -Fred ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Segfault from todays CVS
Hi, On Freitag 18 Februar 2005 17:30, Frederic Bouvier wrote: Are you sure your runtime librairies ( that seems to be compiled with gcc-2.95.3 ) match your compiler ? That is my impression too. 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] segfault in SimGear code
Ron Lange wrote: Hi Gerhard, certainly I examine the variables, as mentioned the last created thread try to access the properties, but the static property pointers don't point to valid memory regions. The 'vel' property node is just the first invalid, where the invalid access occured. The other two property nodes within this scope are invalid, too. Can anyone also cause this segfault by using with an .fgfsrc containing just one line --airport=EDHI --aircraft=bo105 --enable-game-mode Ron, Definitely you should put one option per line. The parser simply wasn't designed to accept input the way you have it. Regards, Curt. -- Curtis Olsonhttp://www.flightgear.org/~curt HumanFIRST Program http://www.humanfirst.umn.edu/ FlightGear Project http://www.flightgear.org Unique text:2f585eeea02e2c79d7b1d8c4963bae2d ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] segfault in SimGear code
Hi Gerhard, certainly I examine the variables, as mentioned the last created thread try to access the properties, but the static property pointers don't point to valid memory regions. The 'vel' property node is just the first invalid, where the invalid access occured. The other two property nodes within this scope are invalid, too. Can anyone also cause this segfault by using with an .fgfsrc containing just one line --airport=EDHI --aircraft=bo105 --enable-game-mode ? Regards Ron Gerhard Wesp schrieb: On Fri, Feb 11, 2005 at 04:14:15PM +0100, Ron Lange wrote: double v = vel-getDoubleValue(); = segfault Can you check vel in the debugger? Just set a breakpoint one line above and enter ``print vel'' (in gdb). Cheers -Gerhard ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] segfault in SimGear code
On Fri, Feb 11, 2005 at 04:14:15PM +0100, Ron Lange wrote: double v = vel-getDoubleValue(); = segfault Can you check vel in the debugger? Just set a breakpoint one line above and enter ``print vel'' (in gdb). Cheers -Gerhard -- Gerhard Wesp o o Tel.: +41 (0) 43 5347636 Bachtobelstrasse 56 | http://www.cosy.sbg.ac.at/~gwesp/ CH-8045 Zuerich \_/ See homepage for email address! ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] segfault in SimGear code
sorry, not the *commandline* below causes fg to break but similar
.fgfsrc file...
fgfs --airport=EDHI --aircraft=bo105 --enable-game-mode
#
Again, only a present .fgfsrc with similar content causes a segfault,
the commandline let fg regulary start.
Second hint: following message appeared twice:
Failed to find runway 28R at airport EDHI --aircraft=bo105
--enable-game-mode
Failed to find a good runway for EDHI --aircraft=bo105 --enable-game-mode
gdb session points on
Autopilot/xmlauto.cxx:804 ff
static void update_helper( double dt ) {
// Estimate speed in 5,10 seconds
static SGPropertyNode *vel = fgGetNode( /velocities/airspeed-kt,
true );
static SGPropertyNode *lookahead5
= fgGetNode( /autopilot/internal/lookahead-5-sec-airspeed-kt,
true );
static SGPropertyNode *lookahead10
= fgGetNode( /autopilot/internal/lookahead-10-sec-airspeed-kt,
true );
static double average = 0.0; // average/filtered prediction
static double v_last = 0.0; // last velocity
double v = vel-getDoubleValue(); = segfault
obvisously the last thread has no longer access to valid property nodes.
Regards
Ron
___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] segfault in SimGear code
On Fri, 11 Feb 2005 16:14:15 +0100 Ron Lange wrote: sorry, not the *commandline* below causes fg to break but similar .fgfsrc file... fgfs --airport=EDHI --aircraft=bo105 --enable-game-mode # Again, only a present .fgfsrc with similar content causes a segfault, the commandline let fg regulary start. Second hint: following message appeared twice: Failed to find runway 28R at airport EDHI --aircraft=bo105 --enable-game-mode Failed to find a good runway for EDHI --aircraft=bo105 --enable-game-mode Could you make sure that there is only one option per line in the .fgfsrc file ? It looks like the parser is trying to set the airport from the string EDHI --aircraft=bo105 --enable-game-mode... -- Jorge Van Hemelryck ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] segfault in SimGear code
Jorge Van Hemelryck wrote: Could you make sure that there is only one option per line in the .fgfsrc file ? It looks like the parser is trying to set the airport from the string EDHI --aircraft=bo105 --enable-game-mode... Aaah, your comment reminds me that the parser is unable to parse multiple options per line from the ~/.fgfsrc file - although I always had the impression that the parser simply ignores the following flags (it still would be nice if the parser could cope with multiple flags), Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] segfault in SimGear code
Hm...hmmm...since putting one flag per line in .fgfsrc wasn't satisfying (not starting from EDHI nor with the bo-105...) I put all flags in one row. Then everything goes as desired but the game mode...after adding enabel-game-mode the segfault appeared. Regards Ron Martin Spott schrieb: Jorge Van Hemelryck wrote: Could you make sure that there is only one option per line in the .fgfsrc file ? It looks like the parser is trying to set the airport from the string EDHI --aircraft=bo105 --enable-game-mode... Aaah, your comment reminds me that the parser is unable to parse multiple options per line from the ~/.fgfsrc file - although I always had the impression that the parser simply ignores the following flags (it still would be nice if the parser could cope with multiple flags), Martin. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] segfault in AI code
Just downloaded a fresh CVS FlightGear and found that the AI code is causing segfaults now. I'll recompile and run it through gdb. In the mean time beware that some aircraft that set up AI scenarios by default, like the T-38 or the hunter-2tanks, are crashing the sim. I've run it through gdb and didn't get any useful output. After a few hours of detective work with cout's I'm getting this: [EMAIL PROTECTED] bin]$ ./t38 FGPropertyManager::GetNode() No node found for fcs/throttle-cmd-norm[0] Creating new property FGPropertyManager::GetNode() No node found for fcs/throttle-cmd-norm[1] Creating new property Starting FGAIManager::bind() Finished FGAIManager::bind() Creating new scenario: refueling_demo Creating an AIAircraft Created an AIAircraft Scenario has been processed. ./t38: line 24: 662 Aborted /home/dave/bin/fgfs $cmdline The sim is crashing before the first call to FGAIManager::update(), however the init() is working fine, and the scenario gets processed and an AI aircraft is created properly. AFAIK the AI subsystem doesn't do anything else between bind() and update(), so the property system (as pointed out by Fred) might be a good place to look. Dave -- David Culp [EMAIL PROTECTED] ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] segfault in AIManager
Just took another look and realized the trace was fine. The bug really is in the animation code. I'll post the patch in a bit. Best, Jim Jim Wilson said: There appears to be something still broken in the AIManager::update(). I'm rebuilding without threads to see if I can get a better backtrace. The crash is moderately intermittent and somewhat random except that it always occurs early on, just a few frames after system initialization (but before scenery loading is complete). I have not been able to reproduce with --disable_ai_models on command line. Best, Jim #0 0x4207afcc in chunk_free () from /lib/i686/libc.so.6 #1 0x4207ad24 in free () from /lib/i686/libc.so.6 #2 0x4006edc6 in __builtin_delete (ptr=0xc37) at ../../gcc/cp/new2.cc:-1 #3 0x084cc1f0 in SGTexMultipleAnimation::~SGTexMultipleAnimation (this=0xc1db498, __in_chrg=3) at animation.cxx:909 #4 0x085465c7 in ssgDeRefDelete (s=0xc1db498) at ssg.cxx:89 #5 0x085496d5 in ssgBase::~ssgBase (this=0xc36fee8, __in_chrg=0) at ssgBase.cxx:75 #6 0x0854d2ae in ssgEntity::~ssgEntity (this=0xc36fee8, __in_chrg=0) at ssgEntity.cxx:53 #7 0x08549bde in ssgBranch::~ssgBranch (this=0xc36fee8, __in_chrg=0) at ssgBranch.cxx:60 #8 0x0859bc0d in ssgBaseTransform::~ssgBaseTransform (this=0xc36fee8, __in_chrg=0) at ssgBaseTransform.cxx:50 #9 0x0855b70d in ssgTexTrans::~ssgTexTrans (this=0xc36fee8, __in_chrg=3) at ssgTexTrans.cxx:53 #10 0x085465c7 in ssgDeRefDelete (s=0xc36fee8) at ssg.cxx:89 #11 0x08549d7a in ssgBranch::removeKid (this=0xc364c38, n=8) at ssgBranch.cxx:97 #12 0x08549dde in ssgBranch::removeAllKids (this=0xc364c38) at ssgBranch.cxx:112 #13 0x08549bc7 in ssgBranch::~ssgBranch (this=0xc364c38, __in_chrg=3) at ssgBranch.cxx:59 #14 0x085465c7 in ssgDeRefDelete (s=0xc364c38) at ssg.cxx:89 #15 0x08549d7a in ssgBranch::removeKid (this=0xc254e58, n=0) at ssgBranch.cxx:97 #16 0x08549dde in ssgBranch::removeAllKids (this=0xc254e58) at ssgBranch.cxx:112 #17 0x08549bc7 in ssgBranch::~ssgBranch (this=0xc254e58, __in_chrg=0) at ssgBranch.cxx:59 #18 0x0859bc0d in ssgBaseTransform::~ssgBaseTransform (this=0xc254e58, __in_chrg=0) at ssgBaseTransform.cxx:50 #19 0x0855c2d5 in ssgTransform::~ssgTransform (this=0xc254e58, __in_chrg=3) at ssgTransform.cxx:53 #20 0x085465c7 in ssgDeRefDelete (s=0xc254e58) at ssg.cxx:89 #21 0x08549d7a in ssgBranch::removeKid (this=0xc07a3d8, n=0) at ssgBranch.cxx:97 #22 0x08549dde in ssgBranch::removeAllKids (this=0xc07a3d8) at ssgBranch.cxx:112 #23 0x08549bc7 in ssgBranch::~ssgBranch (this=0xc07a3d8, __in_chrg=3) at ssgBranch.cxx:59 #24 0x085465c7 in ssgDeRefDelete (s=0xc07a3d8) at ssg.cxx:89 #25 0x08549d7a in ssgBranch::removeKid (this=0xc2e8fd8, n=0) at ssgBranch.cxx:97 #26 0x08549dde in ssgBranch::removeAllKids (this=0xc2e8fd8) at ssgBranch.cxx:112 #27 0x08549bc7 in ssgBranch::~ssgBranch (this=0xc2e8fd8, __in_chrg=0) at ssgBranch.cxx:59 #28 0x0859bc0d in ssgBaseTransform::~ssgBaseTransform (this=0xc2e8fd8, __in_chrg=0) at ssgBaseTransform.cxx:50 #29 0x0855c2d5 in ssgTransform::~ssgTransform (this=0xc2e8fd8, __in_chrg=3) at ssgTransform.cxx:53 #30 0x085465c7 in ssgDeRefDelete (s=0xc2e8fd8) at ssg.cxx:89 #31 0x08549d7a in ssgBranch::removeKid (this=0xc27f778, n=0) at ssgBranch.cxx:97 #32 0x08549dde in ssgBranch::removeAllKids (this=0xc27f778) at ssgBranch.cxx:112 #33 0x08549bc7 in ssgBranch::~ssgBranch (this=0xc27f778, __in_chrg=0) at ssgBranch.cxx:59 #34 0x0859bc0d in ssgBaseTransform::~ssgBaseTransform (this=0xc27f778, __in_chrg=0) at ssgBaseTransform.cxx:50 #35 0x0855c2d5 in ssgTransform::~ssgTransform (this=0xc27f778, __in_chrg=3) at ssgTransform.cxx:53 #36 0x085465c7 in ssgDeRefDelete (s=0xc27f778) at ssg.cxx:89 #37 0x08549d7a in ssgBranch::removeKid (this=0xbea9d08, n=73) at ssgBranch.cxx:97 #38 0x08549dde in ssgBranch::removeAllKids (this=0xbea9d08) at ssgBranch.cxx:112 #39 0x08549bc7 in ssgBranch::~ssgBranch (this=0xbea9d08, __in_chrg=3) at ssgBranch.cxx:59 #40 0x085465c7 in ssgDeRefDelete (s=0xbea9d08) at ssg.cxx:89 #41 0x08549d7a in ssgBranch::removeKid (this=0xc08d868, n=0) at ssgBranch.cxx:97 #42 0x08549dde in ssgBranch::removeAllKids (this=0xc08d868) at ssgBranch.cxx:112 #43 0x08549bc7 in ssgBranch::~ssgBranch (this=0xc08d868, __in_chrg=0) at ssgBranch.cxx:59 #44 0x0859bc0d in ssgBaseTransform::~ssgBaseTransform (this=0xc08d868, __in_chrg=0) at ssgBaseTransform.cxx:50 #45 0x0855c2d5 in ssgTransform::~ssgTransform (this=0xc08d868, __in_chrg=3) at ssgTransform.cxx:53 #46 0x085465c7 in ssgDeRefDelete (s=0xc08d868) at ssg.cxx:89 #47 0x08549d7a in ssgBranch::removeKid (this=0xbe0ce50, n=0) at ssgBranch.cxx:97 #48 0x08549dde in ssgBranch::removeAllKids (this=0xbe0ce50) at ssgBranch.cxx:112 #49 0x08549bc7 in ssgBranch::~ssgBranch (this=0xbe0ce50, __in_chrg=0) at ssgBranch.cxx:59 #50 0x0859bc0d in ssgBaseTransform::~ssgBaseTransform (this=0xbe0ce50, __in_chrg=0) at ssgBaseTransform.cxx:50 #51 0x0855c2d5 in
Re: [Flightgear-devel] Segfault starting up
Try the airport code in all caps ... this used to be more robust to
non-matching codes, not sure what changed but we should probably look
into it.
Regards,
Curt.
Sydney Weidman writes:
Not sure if I should ask about this problem here or in the user list but
here goes:
I tried to start fg up at my local airport, cywg, but it segfaults. ksfo
works fine. I'm using the follwing software:
Linux RedHat 7.3
FlightGear-0.9.2
metakit-2.4.9.2
plib-1.6.0
SimGear-0.3.3
compiled with gcc-3.3
using scenery files w100n40.tar.gz and w100n50.tar.gz
The command i used to start it was:
fgfs --enable-game-mode --airport=cwyg
I didn't find a core file or anything, so I tried to do an strace. Here
are the last few lines:
open(/usr/local/lib/FlightGear/data/Airports/runways.mk4, O_RDONLY) =
7
fcntl64(7, F_SETFD, FD_CLOEXEC) = 0
fstat64(7, {st_mode=S_IFREG|0644, st_size=991200, ...}) = 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0x40d8f000
_llseek(7, 0, [0], SEEK_CUR)= 0
fstat64(7, {st_mode=S_IFREG|0644, st_size=991200, ...}) = 0
_llseek(7, 987136, [987136], SEEK_SET) = 0
read(7, ..., 4064) = 4064
_llseek(7, 0, [0], SEEK_SET)= 0
mmap2(NULL, 991200, PROT_READ, MAP_SHARED, 7, 0) = 0x412dd000
fstat64(7, {st_mode=S_IFREG|0644, st_size=991200, ...}) = 0
_llseek(7, 987136, [987136], SEEK_SET) = 0
read(7, ..., 4064) = 4064
_llseek(7, 0, [0], SEEK_SET)= 0
_llseek(7, 987136, [987136], SEEK_SET) = 0
read(7, ..., 4056) = 4056
read(7, \200\0\0r\0\17\37^, 4096) = 8
_llseek(7, 987136, [987136], SEEK_SET) = 0
read(7, ..., 4096) = 4064
_llseek(7, 0, [0], SEEK_SET)= 0
read(7, JL\32\0\0\17\37\340CZML\0EDKA\0EKYT\0EKYT\0EDPA..., 4096) =
4096
fstat64(7, {st_mode=S_IFREG|0644, st_size=991200, ...}) = 0
_llseek(7, 987136, [987136], SEEK_SET) = 0
read(7, ..., 4096) = 4064
_llseek(7, 0, [0], SEEK_SET)= 0
read(7, JL\32\0\0\17\37\340CZML\0EDKA\0EKYT\0EKYT\0EDPA..., 4096) =
4096
brk(0x8f95000) = 0x8f95000
brk(0x8faa000) = 0x8faa000
brk(0x8fbf000) = 0x8fbf000
brk(0x8fd4000) = 0x8fd4000
brk(0x8fe9000) = 0x8fe9000
brk(0x8ffe000) = 0x8ffe000
brk(0x9013000) = 0x9013000
brk(0x9028000) = 0x9028000
brk(0x903d000) = 0x903d000
brk(0x9052000) = 0x9052000
write(2, A, 1)= 1
write(2, t, 1)= 1
write(2, t, 1)= 1
write(2, e, 1)= 1
write(2, m, 1)= 1
write(2, p, 1)= 1
write(2, t, 1)= 1
write(2, i, 1)= 1
write(2, n, 1)= 1
write(2, g, 1)= 1
write(2, , 1)= 1
write(2, t, 1)= 1
write(2, o, 1)= 1
write(2, , 1)= 1
write(2, s, 1)= 1
write(2, e, 1)= 1
write(2, t, 1)= 1
write(2, , 1)= 1
write(2, s, 1)= 1
write(2, t, 1)= 1
write(2, a, 1)= 1
write(2, r, 1)= 1
write(2, t, 1)= 1
write(2, i, 1)= 1
write(2, n, 1)= 1
write(2, g, 1)= 1
write(2, , 1)= 1
write(2, p, 1)= 1
write(2, o, 1)= 1
write(2, s, 1)= 1
write(2, i, 1)= 1
write(2, t, 1)= 1
write(2, i, 1)= 1
write(2, o, 1)= 1
write(2, n, 1)= 1
write(2, , 1)= 1
write(2, f, 1)= 1
write(2, o, 1)= 1
write(2, r, 1)= 1
write(2, , 1)= 1
write(2, c, 1)= 1
write(2, w, 1)= 1
write(2, y, 1)= 1
write(2, g, 1)= 1
write(2, :, 1)= 1
write(2, 2, 1)= 1
write(2, 8, 1)= 1
write(2, L, 1)= 1
write(2, \n, 1) = 1
--- SIGSEGV (Segmentation fault) ---
+++ killed by SIGSEGV +++
___
Flightgear-devel mailing list
[EMAIL
Re: [Flightgear-devel] segfault on exit
Frederic Bouvier wrote: Please ignore my previous patch. It only produce white splash. Instead, please apply the one below. The memory is deleted in the destructor. Well, that way the texture data is kept in memory at three different places: 1. Main memory (because of your patch) 2. Main memory (OpenGL driver) 3. Texture memory. We should be able to delete the texture data after sending it to OpenGL. Erik ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] segfault on exit
Erik Hofman wrote : Frederic Bouvier wrote: Please ignore my previous patch. It only produce white splash. Instead, please apply the one below. The memory is deleted in the destructor. Well, that way the texture data is kept in memory at three different places: 1. Main memory (because of your patch) 2. Main memory (OpenGL driver) 3. Texture memory. We should be able to delete the texture data after sending it to OpenGL. Are you sure 1. and 2. are separate areas ? Is the copy specified in OpenGL ? After I submitted the first patch, I noticed 2 white splash in a row, then I removed the delete and the clear of the pointer and the white splash disappeared. I can make more test this evening to be sure. -Fred ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] segfault on exit
Frederic BOUVIER wrote:
Erik Hofman wrote :
Frederic Bouvier wrote:
Please ignore my previous patch. It only produce white splash. Instead,
please apply the one below. The memory is deleted in the destructor.
Well, that way the texture data is kept in memory at three different places:
1. Main memory (because of your patch)
2. Main memory (OpenGL driver)
3. Texture memory.
We should be able to delete the texture data after sending it to OpenGL.
Are you sure 1. and 2. are separate areas ? Is the copy specified in
OpenGL ?
After I submitted the first patch, I noticed 2 white splash in a row, then I
removed the delete and the clear of the pointer and the white splash
disappeared.
I can make more test this evening to be sure.
It seems that SGTexture makes the assumption that when texture_data is null,
the texture is not yet created, without looking at texture_id.
For example,
void
SGTexture::finish(unsigned int width, unsigned int height) {
// If a texture hasn't been created then it gets created, and the contents
// of the frame buffer gets copied into it. If the texture has already been
// created then its contents just get updated.
bind();
if (!texture_data)
{
// Copies the contents of the frame buffer into the texture
glCopyTexImage2D(GL_TEXTURE_2D, 0, GL_RGB, 0, 0,
texture_width, texture_height, 0);
} else {
// Copies the contents of the frame buffer into the texture
glCopyTexSubImage2D(GL_TEXTURE_2D, 0, 0, 0, 0, 0,
texture_width, texture_height);
}
// Set the OpenGL window back to its previous size
resize(width, height);
// Clear the window back to black
glClearColor(0.0, 0.0, 0.0, 1.0);
glClear(GL_COLOR_BUFFER_BIT | GL_DEPTH_BUFFER_BIT);
}
The test is on texture_data and not texture_id
-Fred
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] segfault on exit
I wrote : Erik Hofman wrote: Curtis L. Olson wrote: I'm getting a seg fault on exit these days somewhere in ~SGTexture. I haven't investigated further than that ... anyone have any ideas? I am not seeing this. Could it be the result of a stale object file? I am seeing the same problem with MSVC and we need to apply the patch below to fix it. Otherwise, there is a double deletion of the same memory, in the destructor. Please ignore my previous patch. It only produce white splash. Instead, please apply the one below. The memory is deleted in the destructor. Thanks, -Fred D:\FlightGear\cvs\SimGear\simgear\screencvs -q diff -u texture.hxx Index: texture.hxx === RCS file: /var/cvs/SimGear-0.3/SimGear/simgear/screen/texture.hxx,v retrieving revision 1.3 diff -u -r1.3 texture.hxx --- texture.hxx 1 Jul 2003 09:49:45 - 1.3 +++ texture.hxx 9 Jul 2003 20:53:20 - @@ -109,8 +109,6 @@ glTexImage2D( GL_TEXTURE_2D, 0, GL_RGB, texture_width, texture_height, 0, GL_RGB, GL_UNSIGNED_BYTE, texture_data ); - -delete texture_data; } // Nowhere does it say that resident textures have to be in video memory! ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
re: [Flightgear-devel] Segfault fixed
Dave Perry writes: PS The dc3 is still broken. When I try to start the 2nd engine, the mag switch moves, but nothing else happens. You need to advance the magneto as well, probably. All the best, David -- David Megginson, [EMAIL PROTECTED], http://www.megginson.com/ ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
re: [Flightgear-devel] Segfault fixed
David Megginson writes: Dave Perry writes: PS The dc3 is still broken. When I try to start the 2nd engine, the mag switch moves, but nothing else happens. You need to advance the magneto as well, probably. David, give it a try ... actually my guess is that due to the gear problem, it probably crashes instantly so nothing will work at all with it. And of course, in air starts don't work for YAsim models, so... :-) Andy, I'd be happy if we were forced to specify velocity in kts (and then maybe mach for the faster aircraft.) Regards, Curt. -- Curtis Olson IVLab / HumanFIRST Program FlightGear Project Twin Cities[EMAIL PROTECTED] [EMAIL PROTECTED] Minnesota http://www.menet.umn.edu/~curt http://www.flightgear.org ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
re: [Flightgear-devel] Segfault fixed
Curtis L. Olson writes: David, give it a try ... actually my guess is that due to the gear problem, it probably crashes instantly so nothing will work at all with it. And of course, in air starts don't work for YAsim models, so... :-) Andy, I'd be happy if we were forced to specify velocity in kts (and then maybe mach for the faster aircraft.) You're absolutely correct, it's the crash. If you start in mid-air, both engines are fine (though since YASim doesn't allow an initial forward velocity, you will be plummeting rather fast): fgfs --aircraft=dc3 --altitude=1 All the best, David -- David Megginson, [EMAIL PROTECTED], http://www.megginson.com/ ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Segfault
The ovState crash seems like it might have been a transient bug in plib for a while and was fixed I'm running with plib-1.6.0 here, but if you are running cvs version, you might consider doing a cvs update and reinstalling (and make sure you don't have a packaged version installed someplace too.) Regards, Curt. Norman Vine writes: Dave Perry writes: Norman Vine wrote: please enter 'backtrace full' in the gdb window immediately after gdb reports the Segmentation fault and post the results Dave Perry writes: Here is the bactrace. Tile not found (Ok if initializing) scheduling needed tiles for -122.358 37.6117 load() base = /usr/local/FlightGear/Scenery Loading tile /usr/local/FlightGear/Scenery/w010n00/w001n00/2938503 Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 8192 (LWP 1886)] 0x082b9bf9 in ssgContext::forceBasicState() (this=0x8aa7008) at ssgContext.cxx:101 warning: Source file is more recent than executable. ^^^ Are you sure that you are using the PLIB files that you compiled Not really sure how you check that on Linux but I would at least look in /usr/local/lib and /usr/lib. Norman ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel -- Curtis Olson IVLab / HumanFIRST Program FlightGear Project Twin Cities[EMAIL PROTECTED] [EMAIL PROTECTED] Minnesota http://www.menet.umn.edu/~curt http://www.flightgear.org ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Segfault
William Earnest wrote: Dave Perry wrote: Again, an old copy of the the base with bin/fgfs (compiled early in December) runs fine. Regards, Dave I've sent a patch to Curtis which fixes a possible core dump when /sim/systems/electrical/path has not been defined in the aircraft-set.xml file. Which aircraft are you trying to load when this happens? Erik ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Segfault
Dave Perry writes; Bill Earnest wrote: Norman Vine wrote: / Dave Perry // //Here is the last few lines before the segmentation fault. // //Loading tile /usr/local/FlightGear/Scenery/w010n00/w001n00/2938503 // // Did you update the fgBase files from CVS too ? I renamed the base package and got a fresh cvs co of the base package and then updated plib, SimGear, and FlightGear sources from cvs last night and did a make distclean and recompiled plib, then SimGear, and finaly FlightGear. I still get the segfault in the same place. Can you post a backtrace from the debugger so we can see where it's crashing? Norman ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Segfault
Dave Perry wrote: Erik wrote: I've sent a patch to Curtis which fixes a possible core dump when /sim/systems/electrical/path has not been defined in the aircraft-set.xml file. Which aircraft are you trying to load when this happens? Erik, I have tried a number of different aircraft including the default, the a4, c172p-3d, c172-3d-yasim, and the dc3. That must be unrelated than. Sorry. Erik ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Segfault
Dave Perry writes Here is the gdb text after the model is complete to the segfault: leave NewTgtAirportInit()start of fgInitProps() end of fgInitProps() [New Thread 8192 (LWP 1557)] Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 8192 (LWP 1557)] 0x082b9bfc in ssgContext::forceBasicState() (this=0x8aa6fe0) at ssgContext.cxx:101 101 if ( ovState != NULL ) (gdb) q The program is running. Exit anyway? (y or n) Is this enough, or did I not use the right gdb commands? please enter 'backtrace full' in the gdb window immediately after gdb reports the Segmentation fault and post the results Note entering 'help backtrace' in the gdb window will give you an explanation of what we are doing Norman ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Segfault
Dave Perry writes: Norman Vine wrote: please enter 'backtrace full' in the gdb window immediately after gdb reports the Segmentation fault and post the results Dave Perry writes: Here is the bactrace. Tile not found (Ok if initializing) scheduling needed tiles for -122.358 37.6117 load() base = /usr/local/FlightGear/Scenery Loading tile /usr/local/FlightGear/Scenery/w010n00/w001n00/2938503 Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 8192 (LWP 1886)] 0x082b9bf9 in ssgContext::forceBasicState() (this=0x8aa7008) at ssgContext.cxx:101 warning: Source file is more recent than executable. ^^^ Are you sure that you are using the PLIB files that you compiled Not really sure how you check that on Linux but I would at least look in /usr/local/lib and /usr/lib. Norman ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Segfault
Dave Perry wrote: Bill Earnest wrote: Norman Vine wrote: / Dave Perry // // //Here is the last few lines before the segmentation fault. // // //Panel visible = 0 //Playing audio after 0 sec: rumble //Playing audio after 0 sec: squeal //Tile not found (Ok if initializing) //scheduling needed tiles for -122.358 37.6117 //load() base = /usr/local/FlightGear/Scenery //Loading tile /usr/local/FlightGear/Scenery/w010n00/w001n00/2938503 //Segmentation fault // //FWIW, the directory ///usr/local/FlightGear/Scenery/w010n00 //is empty. // // // Hmm... I have seen this before ... // // Did you update the fgBase files from CVS too ? // // Norman // // ___ // Flightgear-devel mailing list // [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] // http://mail.flightgear.org/mailman/listinfo/flightgear-devel // // /Norman, Yes, current CVS of plib, SimGear, FlightGear, and base package. I use a script that pulls all of these at the same time. Only deviation is a 1 week backoff of plib from when the joystick library changes caused some problems. Bill, Did you ever get past this segmentation fault? I renamed the base package and got a fresh cvs co of the base package and then updated plib, SimGear, and FlightGear sources from cvs last night and did a make distclean and recompiled plib, then SimGear, and finaly FlightGear. I still get the segfault in the same place. Again, an old copy of the the base with bin/fgfs (compiled early in December) runs fine. Regards, Dave ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel Dave, No, but then I haven't had much time to work on it. Getting ready for a trip that will last until the new year. At that point I plan to make a clean start CVS pull and see where things stand. Maybe a fresh try will show what I am overlooking. -- Bill Earnest wde3@ptd-dot-net Linux Powered Allentown, PA, USA Computers, like air conditioners, work poorly with Windows open. ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Segfault
Dave Perry wrote: Here is the last few lines before the segmentation fault. Panel visible = 0 Playing audio after 0 sec: rumble Playing audio after 0 sec: squeal Tile not found (Ok if initializing) scheduling needed tiles for -122.358 37.6117 load() base = /usr/local/FlightGear/Scenery Loading tile /usr/local/FlightGear/Scenery/w010n00/w001n00/2938503 Segmentation fault FWIW, the directory /usr/local/FlightGear/Scenery/w010n00 is empty. Again, RH8.0 updated to 2.4.18-18.8.0 kernel AMD XP 1800+ with 512MB of PC2100 DDR ASUS A7m266 mother board ASUS V8200 Deluxe (GF3) with Nvidia 1.0-4191 driver and GLX All works with other Open GL aplications (e.g. Heavy Gear II and tuxracer). All works with 8.0 fgfs. Is anyone else experiencing this? - Dave ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel Hello, That is the identical sequence of error messages I have been getting with the latest development CVS and a recent Cygwin installation. Reported it here a couple of weeks ago. Seems like the KSFO coordinates (which it shows) are getting lost and it looks for data at lat/lon 0,0. -- Bill Earnest wde3@ptd-dot-net Linux Powered Allentown, PA, USA Computers, like air conditioners, work poorly with Windows open. ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Segfault
Dave Perry Here is the last few lines before the segmentation fault. Panel visible = 0 Playing audio after 0 sec: rumble Playing audio after 0 sec: squeal Tile not found (Ok if initializing) scheduling needed tiles for -122.358 37.6117 load() base = /usr/local/FlightGear/Scenery Loading tile /usr/local/FlightGear/Scenery/w010n00/w001n00/2938503 Segmentation fault FWIW, the directory /usr/local/FlightGear/Scenery/w010n00 is empty. Hmm... I have seen this before ... Did you update the fgBase files from CVS too ? Norman ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Segfault
Norman Vine wrote: Dave Perry Here is the last few lines before the segmentation fault. Panel visible = 0 Playing audio after 0 sec: rumble Playing audio after 0 sec: squeal Tile not found (Ok if initializing) scheduling needed tiles for -122.358 37.6117 load() base = /usr/local/FlightGear/Scenery Loading tile /usr/local/FlightGear/Scenery/w010n00/w001n00/2938503 Segmentation fault FWIW, the directory /usr/local/FlightGear/Scenery/w010n00 is empty. Hmm... I have seen this before ... Did you update the fgBase files from CVS too ? Norman ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel Norman, Yes, current CVS of plib, SimGear, FlightGear, and base package. I use a script that pulls all of these at the same time. Only deviation is a 1 week backoff of plib from when the joystick library changes caused some problems. -- Bill Earnest wde3@ptd-dot-net Linux Powered Allentown, PA, USA Computers, like air conditioners, work poorly with Windows open. ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Segfault
William Earnest writes: Norman Vine wrote: Dave Perry Here is the last few lines before the segmentation fault. load() base = /usr/local/FlightGear/Scenery Loading tile /usr/local/FlightGear/Scenery/w010n00/w001n00/2938503 Segmentation fault FWIW, the directory /usr/local/FlightGear/Scenery/w010n00 is empty. Hmm... I have seen this before ... Did you update the fgBase files from CVS too ? Yes, current CVS of plib, SimGear, FlightGear, and base package. I use a script that pulls all of these at the same time. good way todo that :-) Did you check the XML config files for any cvs 'cruft' % cd %FG_ROOT % find . -name '*.xml' -print | xargs grep -n '' /dev/null HTH Norman ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] segfault
Michael Selig writes:
I am trying to compile and run the latest version of fgfs, but I have
hit a problem. When I run it I promptly get the error message
Segmentation Fault
There are no other messages.
(gdb) run
Starting program:
/home/m-seligSim/www-flightgear-org/./FlightGear/src/Main/fgfs
[New Thread 1024 (LWP 21926)]
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 1024 (LWP 21926)]
__strtol_internal (nptr=0x8833618 , endptr=0x85ccee0, base=139597448,
group=1065353216) at eval.c:36
36 eval.c: No such file or directory.
in eval.c
(gdb) bt
#0 __strtol_internal (nptr=0x8833618 , endptr=0x85ccee0, base=139597448,
group=1065353216) at eval.c:36
#1 0x0834b82a in SkyTextureState::SkyTextureState (this=0x8833618)
at SkyTextureState.cpp:47
Michael
Try protecting the call to sgClouds3d-Resize() in main.cxx
void fgReshape( int width, int height ) {
.
if ( fgGetBool(/sim/rendering/clouds3d) ) {
sgClouds3d-Resize( viewmgr-get_current_view()-get_h_fov(),
viewmgr-get_current_view()-get_v_fov() );
}
}
You will still need to run with the --disable-clouds3d option
HTH
Norman
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] segfault
From: Michael Selig [EMAIL PROTECTED] At 10/23/02, Curtis Olson wrote: I'm not coming up with any good ideas ... I *thought* that if you didn't specify --enable-clouds3d, then none of that code was executed, but perhaps that's not the case ... (?) From gdb, it's dying in the 3d cloud setup/init but beyond that I'm not sure why. Ok, given that it's in the new 3D cloud code, maybe some mods could be made so that none of that code gets executed w/ the default, which is 3D clouds off? I love to see those clouds ... but I'd be happy w/ the essentials for now. This thread seems relevant to your problem : http://seneca.me.umn.edu/pipermail/flightgear-devel/2002-September/011441.ht ml Cheers, -Fred ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] segfault
Michael Selig writes: At 10/23/02, Curtis Olson wrote: I'm not coming up with any good ideas ... I *thought* that if you didn't specify --enable-clouds3d, then none of that code was executed, but perhaps that's not the case ... (?) From gdb, it's dying in the 3d cloud setup/init but beyond that I'm not sure why. Ok, given that it's in the new 3D cloud code, maybe some mods could be made so that none of that code gets executed w/ the default, which is 3D clouds off? I love to see those clouds ... but I'd be happy w/ the essentials for now. In src/Main/main.cxx, line #230 we have: SkySceneLoader *sgClouds3d; However, this is just a pointer, and I can't find any place where an instance of this object is created. It seems like it couldn't work without it on any system; am I missing something here? Should we #ifdef out all the 3d cloud support (so developers can still conditionally compiled it in) until everything get's fully fleshed out? Curt. -- Curtis Olson IVLab / HumanFIRST Program FlightGear Project Twin Cities[EMAIL PROTECTED] [EMAIL PROTECTED] Minnesota http://www.menet.umn.edu/~curt http://www.flightgear.org ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] segfault
On Wed, 2002-10-23 at 17:39, Michael Selig wrote: I am trying to compile and run the latest version of fgfs, but I have hit a problem. When I run it I promptly get the error message Segmentation Fault There are no other messages. What I have: - Redhat 7.1 - automake 1.6.3 - autoconf 2.53 - plib 1.6.0 - yesterday's cvs of Simgear, fgfsbase, Flightgear (0.9) I am able to compile and run my older version of fgfs (from 8/20/2002) w/ the new plib and Simgear. Also, we're able to compile and run the new setup on some other Redhat machines. So this does seem to be machine specific, but I have not changed anything at the system level. Anyone have any ideas on what I could try next? It may help to know where it's crashing. run fgfs with this: gdb fgfs type run at the gdb prompt then, when it crashes, type bt and post the results. Regards, Michael ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel -- Tony Peden [EMAIL PROTECTED] We all know Linux is great ... it does infinite loops in 5 seconds. -- attributed to Linus Torvalds ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] segfault
At 10/23/02, Tony Peden wrote: On Wed, 2002-10-23 at 17:39, Michael Selig wrote: I am trying to compile and run the latest version of fgfs, but I have hit a problem. When I run it I promptly get the error message Segmentation Fault There are no other messages. What I have: - Redhat 7.1 - automake 1.6.3 - autoconf 2.53 - plib 1.6.0 - yesterday's cvs of Simgear, fgfsbase, Flightgear (0.9) I am able to compile and run my older version of fgfs (from 8/20/2002) w/ the new plib and Simgear. Also, we're able to compile and run the new setup on some other Redhat machines. So this does seem to be machine specific, but I have not changed anything at the system level. Anyone have any ideas on what I could try next? It may help to know where it's crashing. run fgfs with this: gdb fgfs type run at the gdb prompt then, when it crashes, type bt and post the results. Here's what I get: ~/www-flightgear-org gdb ./FlightGear/src/Main/fgfs GNU gdb 5.0rh-5 Red Hat Linux 7.1 Copyright 2001 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as i386-redhat-linux... (gdb) run Starting program: /home/m-seligSim/www-flightgear-org/./FlightGear/src/Main/fgfs [New Thread 1024 (LWP 21926)] Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 1024 (LWP 21926)] __strtol_internal (nptr=0x8833618 , endptr=0x85ccee0, base=139597448, group=1065353216) at eval.c:36 36 eval.c: No such file or directory. in eval.c (gdb) bt #0 __strtol_internal (nptr=0x8833618 , endptr=0x85ccee0, base=139597448, group=1065353216) at eval.c:36 #1 0x0834b82a in SkyTextureState::SkyTextureState (this=0x8833618) at SkyTextureState.cpp:47 #2 0x08348a5f in SkyMaterial::SkyMaterial (this=0x8833578) at SkyMaterial.cpp:60 #3 0x08348223 in SkyLight::SkyLight (this=0x8833500, eType=SKY_LIGHT_DIRECTIONAL) at SkyLight.cpp:67 #4 0x08346ce6 in __static_initialization_and_destruction_0 (__initialize_p=1, __priority=65535) at /usr/include/g++-3/stl_multimap.h:52 #5 0x08346d8e in global constructors keyed to eType () at /usr/include/g++-3/stl_multimap.h:75 #6 0x083fb895 in __do_global_ctors_aux () at slMODfile.cxx:686 #7 0x0804e0ae in _init () at eval.c:41 #8 0x40317161 in __libc_start_main (main=0x80573ec main, argc=1, ubp_av=0xb8ec, init=0x804e098 _init, fini=0x8450e80 _fini, rtld_fini=0x4000e184 _dl_fini, stack_end=0xb8dc) at ../sysdeps/generic/libc-start.c:122 FWIW I have done things like: - uninstall SimGear and plib, and reinstalled. - I have done a cvs co from our uiuc mirror and a cvs update -dP from the fgfs site. I get the same segfault w/ both versions of the code. - As compared w/ the last version that worked, there has been a bunch of new 3D cloud work and runway lighting (I think). - I also installed metakit from the tarball in SimGear/src-lib, but I speculate that I did not really need to do that. - Through all of these gyrations, my version from 8/20/02 still compiles and runs w/ the new SimGear and plib. Regards, Michael Regards, Michael ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel -- Tony Peden [EMAIL PROTECTED] We all know Linux is great ... it does infinite loops in 5 seconds. -- attributed to Linus Torvalds ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] segfault
On Wed, 2002-10-23 at 19:14, Michael Selig wrote: At 10/23/02, Tony Peden wrote: On Wed, 2002-10-23 at 17:39, Michael Selig wrote: I am trying to compile and run the latest version of fgfs, but I have hit a problem. When I run it I promptly get the error message Segmentation Fault There are no other messages. What I have: - Redhat 7.1 - automake 1.6.3 - autoconf 2.53 - plib 1.6.0 - yesterday's cvs of Simgear, fgfsbase, Flightgear (0.9) I am able to compile and run my older version of fgfs (from 8/20/2002) w/ the new plib and Simgear. Also, we're able to compile and run the new setup on some other Redhat machines. So this does seem to be machine specific, but I have not changed anything at the system level. Anyone have any ideas on what I could try next? It may help to know where it's crashing. run fgfs with this: gdb fgfs type run at the gdb prompt then, when it crashes, type bt and post the results. Here's what I get: ~/www-flightgear-org gdb ./FlightGear/src/Main/fgfs GNU gdb 5.0rh-5 Red Hat Linux 7.1 Copyright 2001 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as i386-redhat-linux... (gdb) run Starting program: /home/m-seligSim/www-flightgear-org/./FlightGear/src/Main/fgfs [New Thread 1024 (LWP 21926)] Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 1024 (LWP 21926)] __strtol_internal (nptr=0x8833618 , endptr=0x85ccee0, base=139597448, group=1065353216) at eval.c:36 36 eval.c: No such file or directory. in eval.c (gdb) bt #0 __strtol_internal (nptr=0x8833618 , endptr=0x85ccee0, base=139597448, group=1065353216) at eval.c:36 #1 0x0834b82a in SkyTextureState::SkyTextureState (this=0x8833618) at SkyTextureState.cpp:47 #2 0x08348a5f in SkyMaterial::SkyMaterial (this=0x8833578) at SkyMaterial.cpp:60 #3 0x08348223 in SkyLight::SkyLight (this=0x8833500, eType=SKY_LIGHT_DIRECTIONAL) at SkyLight.cpp:67 #4 0x08346ce6 in __static_initialization_and_destruction_0 (__initialize_p=1, __priority=65535) at /usr/include/g++-3/stl_multimap.h:52 #5 0x08346d8e in global constructors keyed to eType () at /usr/include/g++-3/stl_multimap.h:75 #6 0x083fb895 in __do_global_ctors_aux () at slMODfile.cxx:686 #7 0x0804e0ae in _init () at eval.c:41 #8 0x40317161 in __libc_start_main (main=0x80573ec main, argc=1, ubp_av=0xb8ec, init=0x804e098 _init, fini=0x8450e80 _fini, rtld_fini=0x4000e184 _dl_fini, stack_end=0xb8dc) at ../sysdeps/generic/libc-start.c:122 FWIW I have done things like: - uninstall SimGear and plib, and reinstalled. - I have done a cvs co from our uiuc mirror and a cvs update -dP from the fgfs site. I get the same segfault w/ both versions of the code. - As compared w/ the last version that worked, there has been a bunch of new 3D cloud work and runway lighting (I think). - I also installed metakit from the tarball in SimGear/src-lib, but I speculate that I did not really need to do that. - Through all of these gyrations, my version from 8/20/02 still compiles and runs w/ the new SimGear and plib. Hmm, this looks like its in the 3D clouds code ... you might try running with it disabled using: --disable-clouds3d Beyond that, I'm not going to be much help. Regards, Michael Regards, Michael ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel -- Tony Peden [EMAIL PROTECTED] We all know Linux is great ... it does infinite loops in 5 seconds. -- attributed to Linus Torvalds ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel -- Tony Peden [EMAIL PROTECTED] We all know Linux is great ... it does infinite loops in 5 seconds. -- attributed to Linus Torvalds ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] segfault
At 10/23/02, Tony Peden wrote: On Wed, 2002-10-23 at 19:14, Michael Selig wrote: At 10/23/02, Tony Peden wrote: On Wed, 2002-10-23 at 17:39, Michael Selig wrote: I am trying to compile and run the latest version of fgfs, but I have hit a problem. When I run it I promptly get the error message Segmentation Fault There are no other messages. What I have: - Redhat 7.1 - automake 1.6.3 - autoconf 2.53 - plib 1.6.0 - yesterday's cvs of Simgear, fgfsbase, Flightgear (0.9) I am able to compile and run my older version of fgfs (from 8/20/2002) w/ the new plib and Simgear. Also, we're able to compile and run the new setup on some other Redhat machines. So this does seem to be machine specific, but I have not changed anything at the system level. Anyone have any ideas on what I could try next? It may help to know where it's crashing. run fgfs with this: gdb fgfs type run at the gdb prompt then, when it crashes, type bt and post the results. Here's what I get: ~/www-flightgear-org gdb ./FlightGear/src/Main/fgfs GNU gdb 5.0rh-5 Red Hat Linux 7.1 Copyright 2001 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as i386-redhat-linux... (gdb) run Starting program: /home/m-seligSim/www-flightgear-org/./FlightGear/src/Main/fgfs [New Thread 1024 (LWP 21926)] Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 1024 (LWP 21926)] __strtol_internal (nptr=0x8833618 , endptr=0x85ccee0, base=139597448, group=1065353216) at eval.c:36 36 eval.c: No such file or directory. in eval.c (gdb) bt #0 __strtol_internal (nptr=0x8833618 , endptr=0x85ccee0, base=139597448, group=1065353216) at eval.c:36 #1 0x0834b82a in SkyTextureState::SkyTextureState (this=0x8833618) at SkyTextureState.cpp:47 #2 0x08348a5f in SkyMaterial::SkyMaterial (this=0x8833578) at SkyMaterial.cpp:60 #3 0x08348223 in SkyLight::SkyLight (this=0x8833500, eType=SKY_LIGHT_DIRECTIONAL) at SkyLight.cpp:67 #4 0x08346ce6 in __static_initialization_and_destruction_0 (__initialize_p=1, __priority=65535) at /usr/include/g++-3/stl_multimap.h:52 #5 0x08346d8e in global constructors keyed to eType () at /usr/include/g++-3/stl_multimap.h:75 #6 0x083fb895 in __do_global_ctors_aux () at slMODfile.cxx:686 #7 0x0804e0ae in _init () at eval.c:41 #8 0x40317161 in __libc_start_main (main=0x80573ec main, argc=1, ubp_av=0xb8ec, init=0x804e098 _init, fini=0x8450e80 _fini, rtld_fini=0x4000e184 _dl_fini, stack_end=0xb8dc) at ../sysdeps/generic/libc-start.c:122 FWIW I have done things like: - uninstall SimGear and plib, and reinstalled. - I have done a cvs co from our uiuc mirror and a cvs update -dP from the fgfs site. I get the same segfault w/ both versions of the code. - As compared w/ the last version that worked, there has been a bunch of new 3D cloud work and runway lighting (I think). - I also installed metakit from the tarball in SimGear/src-lib, but I speculate that I did not really need to do that. - Through all of these gyrations, my version from 8/20/02 still compiles and runs w/ the new SimGear and plib. Hmm, this looks like its in the 3D clouds code ... you might try running with it disabled using: --disable-clouds3d Beyond that, I'm not going to be much help. I am still getting the same segfault w/ this option. It even promptly crashes w/ ./fgfs --help i.e. I don't get the option list. Regards, Michael Regards, Michael ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel -- Tony Peden [EMAIL PROTECTED] We all know Linux is great ... it does infinite loops in 5 seconds. -- attributed to Linus Torvalds ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel -- Tony Peden [EMAIL PROTECTED] We all know Linux is great ... it does infinite loops in 5 seconds. -- attributed to Linus Torvalds ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] segfault
Michael Selig writes: I am still getting the same segfault w/ this option. It even promptly crashes w/ ./fgfs --help i.e. I don't get the option list. Are you missing the base package some how, or pointing to the wrong directory? Curt. -- Curtis Olson IVLab / HumanFIRST Program FlightGear Project Twin Cities[EMAIL PROTECTED] [EMAIL PROTECTED] Minnesota http://www.menet.umn.edu/~curt http://www.flightgear.org ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] segfault
I just ran through firing up all the non 172 planes and there are several JSBsim planes that segfault x24b X15 Shuttle On Wednesday 23 October 2002 10:30 pm, Tony Peden wrote: On Wed, 2002-10-23 at 19:14, Michael Selig wrote: At 10/23/02, Tony Peden wrote: On Wed, 2002-10-23 at 17:39, Michael Selig wrote: I am trying to compile and run the latest version of fgfs, but I have hit a problem. When I run it I promptly get the error message Segmentation Fault There are no other messages. What I have: - Redhat 7.1 - automake 1.6.3 - autoconf 2.53 - plib 1.6.0 - yesterday's cvs of Simgear, fgfsbase, Flightgear (0.9) I am able to compile and run my older version of fgfs (from 8/20/2002) w/ the new plib and Simgear. Also, we're able to compile and run the new setup on some other Redhat machines. So this does seem to be machine specific, but I have not changed anything at the system level. Anyone have any ideas on what I could try next? It may help to know where it's crashing. run fgfs with this: gdb fgfs type run at the gdb prompt then, when it crashes, type bt and post the results. Here's what I get: ~/www-flightgear-org gdb ./FlightGear/src/Main/fgfs GNU gdb 5.0rh-5 Red Hat Linux 7.1 Copyright 2001 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as i386-redhat-linux... (gdb) run Starting program: /home/m-seligSim/www-flightgear-org/./FlightGear/src/Main/fgfs [New Thread 1024 (LWP 21926)] Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 1024 (LWP 21926)] __strtol_internal (nptr=0x8833618 , endptr=0x85ccee0, base=139597448, group=1065353216) at eval.c:36 36 eval.c: No such file or directory. in eval.c (gdb) bt #0 __strtol_internal (nptr=0x8833618 , endptr=0x85ccee0, base=139597448, group=1065353216) at eval.c:36 #1 0x0834b82a in SkyTextureState::SkyTextureState (this=0x8833618) at SkyTextureState.cpp:47 #2 0x08348a5f in SkyMaterial::SkyMaterial (this=0x8833578) at SkyMaterial.cpp:60 #3 0x08348223 in SkyLight::SkyLight (this=0x8833500, eType=SKY_LIGHT_DIRECTIONAL) at SkyLight.cpp:67 #4 0x08346ce6 in __static_initialization_and_destruction_0 (__initialize_p=1, __priority=65535) at /usr/include/g++-3/stl_multimap.h:52 #5 0x08346d8e in global constructors keyed to eType () at /usr/include/g++-3/stl_multimap.h:75 #6 0x083fb895 in __do_global_ctors_aux () at slMODfile.cxx:686 #7 0x0804e0ae in _init () at eval.c:41 #8 0x40317161 in __libc_start_main (main=0x80573ec main, argc=1, ubp_av=0xb8ec, init=0x804e098 _init, fini=0x8450e80 _fini, rtld_fini=0x4000e184 _dl_fini, stack_end=0xb8dc) at ../sysdeps/generic/libc-start.c:122 FWIW I have done things like: - uninstall SimGear and plib, and reinstalled. - I have done a cvs co from our uiuc mirror and a cvs update -dP from the fgfs site. I get the same segfault w/ both versions of the code. - As compared w/ the last version that worked, there has been a bunch of new 3D cloud work and runway lighting (I think). - I also installed metakit from the tarball in SimGear/src-lib, but I speculate that I did not really need to do that. - Through all of these gyrations, my version from 8/20/02 still compiles and runs w/ the new SimGear and plib. Hmm, this looks like its in the 3D clouds code ... you might try running with it disabled using: --disable-clouds3d Beyond that, I'm not going to be much help. Regards, Michael Regards, Michael ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel -- Tony Peden [EMAIL PROTECTED] We all know Linux is great ... it does infinite loops in 5 seconds. -- attributed to Linus Torvalds ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] segfault
At 10/23/02, Curtis Olson wrote: Michael Selig writes: I am still getting the same segfault w/ this option. It even promptly crashes w/ ./fgfs --help i.e. I don't get the option list. Are you missing the base package some how, or pointing to the wrong directory? If I run my working old version w/o setting FG_ROOT, I get this: [221] m-selig@qtee:/home/m-seligSim/work ./flightsim-0.7.pre11/src/Main/fgfs FlightGear: Version 0.7.11pre1 Built with GNU C++ version 2.96 Scanning for root: command line fg_root = /home/m-seligSim/www-flightgear-org/fgfsbase Usage: strings/usage strings/general-options: --help, -h strings/help-desc snip For a complete list of options use --help --verbose Base package check failed ... Found version 0.9.0 at: /home/m-seligSim/www-flightgear-org/fgfsbase Please upgrade to version0.7.11pre1 When I run the new one the same way, I get this: [226] m-selig@qtee:/home/m-seligSim/www-flightgear-org ./FlightGear/src/Main/fgfs Segmentation fault So this does not seem to be related to the base package. FWIW I will not rule out that I could be making some mistakes at my end, but I have already tried working this out w/ Rob Deters here. Also, our most recent update follows the steps we have taken before ... and on Rob's computer it is working. He is running Redhat 7.2. I am running 7.1, and that's the only difference on the surface. Still puzzled in Illinois ... and trying very hard to avoid having to reinstall my wonderful Linux box. Curt. -- Curtis Olson IVLab / HumanFIRST Program FlightGear Project Twin Cities[EMAIL PROTECTED] [EMAIL PROTECTED] Minnesota http://www.menet.umn.edu/~curt http://www.flightgear.org ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] segfault
At 10/23/02, John Check wrote: I just ran through firing up all the non 172 planes and there are several JSBsim planes that segfault x24b X15 Shuttle I have been down this road before. These planes are crashing for some reason, and the segfault is not the first thing that happens. This segfault is very different and probably simply FDM related. It seems that a big clue w/ my segfault is that it happens right out of the box, i.e. immediately. On Wednesday 23 October 2002 10:30 pm, Tony Peden wrote: On Wed, 2002-10-23 at 19:14, Michael Selig wrote: At 10/23/02, Tony Peden wrote: On Wed, 2002-10-23 at 17:39, Michael Selig wrote: I am trying to compile and run the latest version of fgfs, but I have hit a problem. When I run it I promptly get the error message Segmentation Fault There are no other messages. What I have: - Redhat 7.1 - automake 1.6.3 - autoconf 2.53 - plib 1.6.0 - yesterday's cvs of Simgear, fgfsbase, Flightgear (0.9) I am able to compile and run my older version of fgfs (from 8/20/2002) w/ the new plib and Simgear. Also, we're able to compile and run the new setup on some other Redhat machines. So this does seem to be machine specific, but I have not changed anything at the system level. Anyone have any ideas on what I could try next? It may help to know where it's crashing. run fgfs with this: gdb fgfs type run at the gdb prompt then, when it crashes, type bt and post the results. Here's what I get: ~/www-flightgear-org gdb ./FlightGear/src/Main/fgfs GNU gdb 5.0rh-5 Red Hat Linux 7.1 Copyright 2001 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as i386-redhat-linux... (gdb) run Starting program: /home/m-seligSim/www-flightgear-org/./FlightGear/src/Main/fgfs [New Thread 1024 (LWP 21926)] Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 1024 (LWP 21926)] __strtol_internal (nptr=0x8833618 , endptr=0x85ccee0, base=139597448, group=1065353216) at eval.c:36 36 eval.c: No such file or directory. in eval.c (gdb) bt #0 __strtol_internal (nptr=0x8833618 , endptr=0x85ccee0, base=139597448, group=1065353216) at eval.c:36 #1 0x0834b82a in SkyTextureState::SkyTextureState (this=0x8833618) at SkyTextureState.cpp:47 #2 0x08348a5f in SkyMaterial::SkyMaterial (this=0x8833578) at SkyMaterial.cpp:60 #3 0x08348223 in SkyLight::SkyLight (this=0x8833500, eType=SKY_LIGHT_DIRECTIONAL) at SkyLight.cpp:67 #4 0x08346ce6 in __static_initialization_and_destruction_0 (__initialize_p=1, __priority=65535) at /usr/include/g++-3/stl_multimap.h:52 #5 0x08346d8e in global constructors keyed to eType () at /usr/include/g++-3/stl_multimap.h:75 #6 0x083fb895 in __do_global_ctors_aux () at slMODfile.cxx:686 #7 0x0804e0ae in _init () at eval.c:41 #8 0x40317161 in __libc_start_main (main=0x80573ec main, argc=1, ubp_av=0xb8ec, init=0x804e098 _init, fini=0x8450e80 _fini, rtld_fini=0x4000e184 _dl_fini, stack_end=0xb8dc) at ../sysdeps/generic/libc-start.c:122 FWIW I have done things like: - uninstall SimGear and plib, and reinstalled. - I have done a cvs co from our uiuc mirror and a cvs update -dP from the fgfs site. I get the same segfault w/ both versions of the code. - As compared w/ the last version that worked, there has been a bunch of new 3D cloud work and runway lighting (I think). - I also installed metakit from the tarball in SimGear/src-lib, but I speculate that I did not really need to do that. - Through all of these gyrations, my version from 8/20/02 still compiles and runs w/ the new SimGear and plib. Hmm, this looks like its in the 3D clouds code ... you might try running with it disabled using: --disable-clouds3d Beyond that, I'm not going to be much help. Regards, Michael Regards, Michael ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel -- Tony Peden [EMAIL PROTECTED] We all know Linux is great ... it does infinite loops in 5 seconds. -- attributed to Linus Torvalds ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel ___ Flightgear-devel mailing list
RE: [Flightgear-devel] segfault
Shuttle and x24b are experimental in JSBSim. The X-15 worked fine at one point - I believe Tony gave a full test of this as part of the testing he did before committing the JSBSim changes involving properties. No major code changes have occurred since then. Few *minor* changes have occurred. Is anyone else seeing this? Jon -Original Message- From: [EMAIL PROTECTED] [mailto:flightgear-devel-admin;flightgear.org]On Behalf Of John Check Sent: Wednesday, October 23, 2002 10:36 PM To: [EMAIL PROTECTED] Subject: Re: [Flightgear-devel] segfault I just ran through firing up all the non 172 planes and there are several JSBsim planes that segfault x24b X15 Shuttle On Wednesday 23 October 2002 10:30 pm, Tony Peden wrote: On Wed, 2002-10-23 at 19:14, Michael Selig wrote: At 10/23/02, Tony Peden wrote: On Wed, 2002-10-23 at 17:39, Michael Selig wrote: I am trying to compile and run the latest version of fgfs, but I have hit a problem. When I run it I promptly get the error message Segmentation Fault There are no other messages. What I have: - Redhat 7.1 - automake 1.6.3 - autoconf 2.53 - plib 1.6.0 - yesterday's cvs of Simgear, fgfsbase, Flightgear (0.9) I am able to compile and run my older version of fgfs (from 8/20/2002) w/ the new plib and Simgear. Also, we're able to compile and run the new setup on some other Redhat machines. So this does seem to be machine specific, but I have not changed anything at the system level. Anyone have any ideas on what I could try next? It may help to know where it's crashing. run fgfs with this: gdb fgfs type run at the gdb prompt then, when it crashes, type bt and post the results. Here's what I get: ~/www-flightgear-org gdb ./FlightGear/src/Main/fgfs GNU gdb 5.0rh-5 Red Hat Linux 7.1 Copyright 2001 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as i386-redhat-linux... (gdb) run Starting program: /home/m-seligSim/www-flightgear-org/./FlightGear/src/Main/fgfs [New Thread 1024 (LWP 21926)] Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 1024 (LWP 21926)] __strtol_internal (nptr=0x8833618 , endptr=0x85ccee0, base=139597448, group=1065353216) at eval.c:36 36 eval.c: No such file or directory. in eval.c (gdb) bt #0 __strtol_internal (nptr=0x8833618 , endptr=0x85ccee0, base=139597448, group=1065353216) at eval.c:36 #1 0x0834b82a in SkyTextureState::SkyTextureState (this=0x8833618) at SkyTextureState.cpp:47 #2 0x08348a5f in SkyMaterial::SkyMaterial (this=0x8833578) at SkyMaterial.cpp:60 #3 0x08348223 in SkyLight::SkyLight (this=0x8833500, eType=SKY_LIGHT_DIRECTIONAL) at SkyLight.cpp:67 #4 0x08346ce6 in __static_initialization_and_destruction_0 (__initialize_p=1, __priority=65535) at /usr/include/g++-3/stl_multimap.h:52 #5 0x08346d8e in global constructors keyed to eType () at /usr/include/g++-3/stl_multimap.h:75 #6 0x083fb895 in __do_global_ctors_aux () at slMODfile.cxx:686 #7 0x0804e0ae in _init () at eval.c:41 #8 0x40317161 in __libc_start_main (main=0x80573ec main, argc=1, ubp_av=0xb8ec, init=0x804e098 _init, fini=0x8450e80 _fini, rtld_fini=0x4000e184 _dl_fini, stack_end=0xb8dc) at ../sysdeps/generic/libc-start.c:122 FWIW I have done things like: - uninstall SimGear and plib, and reinstalled. - I have done a cvs co from our uiuc mirror and a cvs update -dP from the fgfs site. I get the same segfault w/ both versions of the code. - As compared w/ the last version that worked, there has been a bunch of new 3D cloud work and runway lighting (I think). - I also installed metakit from the tarball in SimGear/src-lib, but I speculate that I did not really need to do that. - Through all of these gyrations, my version from 8/20/02 still compiles and runs w/ the new SimGear and plib. Hmm, this looks like its in the 3D clouds code ... you might try running with it disabled using: --disable-clouds3d Beyond that, I'm not going to be much help. Regards, Michael Regards, Michael ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel -- Tony Peden [EMAIL PROTECTED] We all know Linux is great ... it does infinite loops in 5 seconds. -- attributed to Linus Torvalds
RE: [Flightgear-devel] segfault
Can anyone offer some help, here? I do not have a recent build of FlightGear and cannot build it at the moment for reasons I don't want to go into (that have nothing to do with FlightGear or my computer). Can someone copy the log output concerning JSBSim for the X-15 and post it or email to me and Tony? Also, some detailed info and wierdness and/or where it segfaults would be helpful. Platform info, too. Jon -Original Message- From: [EMAIL PROTECTED] [mailto:flightgear-devel-admin;flightgear.org]On Behalf Of Michael Selig Sent: Wednesday, October 23, 2002 10:54 PM To: [EMAIL PROTECTED] Subject: Re: [Flightgear-devel] segfault At 10/23/02, John Check wrote: I just ran through firing up all the non 172 planes and there are several JSBsim planes that segfault x24b X15 Shuttle I have been down this road before. These planes are crashing for some reason, and the segfault is not the first thing that happens. This segfault is very different and probably simply FDM related. It seems that a big clue w/ my segfault is that it happens right out of the box, i.e. immediately. On Wednesday 23 October 2002 10:30 pm, Tony Peden wrote: On Wed, 2002-10-23 at 19:14, Michael Selig wrote: At 10/23/02, Tony Peden wrote: On Wed, 2002-10-23 at 17:39, Michael Selig wrote: I am trying to compile and run the latest version of fgfs, but I have hit a problem. When I run it I promptly get the error message Segmentation Fault There are no other messages. What I have: - Redhat 7.1 - automake 1.6.3 - autoconf 2.53 - plib 1.6.0 - yesterday's cvs of Simgear, fgfsbase, Flightgear (0.9) I am able to compile and run my older version of fgfs (from 8/20/2002) w/ the new plib and Simgear. Also, we're able to compile and run the new setup on some other Redhat machines. So this does seem to be machine specific, but I have not changed anything at the system level. Anyone have any ideas on what I could try next? It may help to know where it's crashing. run fgfs with this: gdb fgfs type run at the gdb prompt then, when it crashes, type bt and post the results. Here's what I get: ~/www-flightgear-org gdb ./FlightGear/src/Main/fgfs GNU gdb 5.0rh-5 Red Hat Linux 7.1 Copyright 2001 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as i386-redhat-linux... (gdb) run Starting program: /home/m-seligSim/www-flightgear-org/./FlightGear/src/Main/fgfs [New Thread 1024 (LWP 21926)] Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 1024 (LWP 21926)] __strtol_internal (nptr=0x8833618 , endptr=0x85ccee0, base=139597448, group=1065353216) at eval.c:36 36 eval.c: No such file or directory. in eval.c (gdb) bt #0 __strtol_internal (nptr=0x8833618 , endptr=0x85ccee0, base=139597448, group=1065353216) at eval.c:36 #1 0x0834b82a in SkyTextureState::SkyTextureState (this=0x8833618) at SkyTextureState.cpp:47 #2 0x08348a5f in SkyMaterial::SkyMaterial (this=0x8833578) at SkyMaterial.cpp:60 #3 0x08348223 in SkyLight::SkyLight (this=0x8833500, eType=SKY_LIGHT_DIRECTIONAL) at SkyLight.cpp:67 #4 0x08346ce6 in __static_initialization_and_destruction_0 (__initialize_p=1, __priority=65535) at /usr/include/g++-3/stl_multimap.h:52 #5 0x08346d8e in global constructors keyed to eType () at /usr/include/g++-3/stl_multimap.h:75 #6 0x083fb895 in __do_global_ctors_aux () at slMODfile.cxx:686 #7 0x0804e0ae in _init () at eval.c:41 #8 0x40317161 in __libc_start_main (main=0x80573ec main, argc=1, ubp_av=0xb8ec, init=0x804e098 _init, fini=0x8450e80 _fini, rtld_fini=0x4000e184 _dl_fini, stack_end=0xb8dc) at ../sysdeps/generic/libc-start.c:122 FWIW I have done things like: - uninstall SimGear and plib, and reinstalled. - I have done a cvs co from our uiuc mirror and a cvs update -dP from the fgfs site. I get the same segfault w/ both versions of the code. - As compared w/ the last version that worked, there has been a bunch of new 3D cloud work and runway lighting (I think). - I also installed metakit from the tarball in SimGear/src-lib, but I speculate that I did not really need to do that. - Through all of these gyrations, my version from 8/20/02 still compiles and runs w/ the new SimGear and plib. Hmm, this looks like its in the 3D clouds code ... you might try running with it disabled using
RE: [Flightgear-devel] segfault
I'm not coming up with any good ideas ... I *thought* that if you didn't specify --enable-clouds3d, then none of that code was executed, but perhaps that's not the case ... (?) From gdb, it's dying in the 3d cloud setup/init but beyond that I'm not sure why. Curt. Jon Berndt writes: Can anyone offer some help, here? I do not have a recent build of FlightGear and cannot build it at the moment for reasons I don't want to go into (that have nothing to do with FlightGear or my computer). Can someone copy the log output concerning JSBSim for the X-15 and post it or email to me and Tony? Also, some detailed info and wierdness and/or where it segfaults would be helpful. Platform info, too. Jon -Original Message- From: [EMAIL PROTECTED] [mailto:flightgear-devel-admin;flightgear.org]On Behalf Of Michael Selig Sent: Wednesday, October 23, 2002 10:54 PM To: [EMAIL PROTECTED] Subject: Re: [Flightgear-devel] segfault At 10/23/02, John Check wrote: I just ran through firing up all the non 172 planes and there are several JSBsim planes that segfault x24b X15 Shuttle I have been down this road before. These planes are crashing for some reason, and the segfault is not the first thing that happens. This segfault is very different and probably simply FDM related. It seems that a big clue w/ my segfault is that it happens right out of the box, i.e. immediately. On Wednesday 23 October 2002 10:30 pm, Tony Peden wrote: On Wed, 2002-10-23 at 19:14, Michael Selig wrote: At 10/23/02, Tony Peden wrote: On Wed, 2002-10-23 at 17:39, Michael Selig wrote: I am trying to compile and run the latest version of fgfs, but I have hit a problem. When I run it I promptly get the error message Segmentation Fault There are no other messages. What I have: - Redhat 7.1 - automake 1.6.3 - autoconf 2.53 - plib 1.6.0 - yesterday's cvs of Simgear, fgfsbase, Flightgear (0.9) I am able to compile and run my older version of fgfs (from 8/20/2002) w/ the new plib and Simgear. Also, we're able to compile and run the new setup on some other Redhat machines. So this does seem to be machine specific, but I have not changed anything at the system level. Anyone have any ideas on what I could try next? It may help to know where it's crashing. run fgfs with this: gdb fgfs type run at the gdb prompt then, when it crashes, type bt and post the results. Here's what I get: ~/www-flightgear-org gdb ./FlightGear/src/Main/fgfs GNU gdb 5.0rh-5 Red Hat Linux 7.1 Copyright 2001 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as i386-redhat-linux... (gdb) run Starting program: /home/m-seligSim/www-flightgear-org/./FlightGear/src/Main/fgfs [New Thread 1024 (LWP 21926)] Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 1024 (LWP 21926)] __strtol_internal (nptr=0x8833618 , endptr=0x85ccee0, base=139597448, group=1065353216) at eval.c:36 36 eval.c: No such file or directory. in eval.c (gdb) bt #0 __strtol_internal (nptr=0x8833618 , endptr=0x85ccee0, base=139597448, group=1065353216) at eval.c:36 #1 0x0834b82a in SkyTextureState::SkyTextureState (this=0x8833618) at SkyTextureState.cpp:47 #2 0x08348a5f in SkyMaterial::SkyMaterial (this=0x8833578) at SkyMaterial.cpp:60 #3 0x08348223 in SkyLight::SkyLight (this=0x8833500, eType=SKY_LIGHT_DIRECTIONAL) at SkyLight.cpp:67 #4 0x08346ce6 in __static_initialization_and_destruction_0 (__initialize_p=1, __priority=65535) at /usr/include/g++-3/stl_multimap.h:52 #5 0x08346d8e in global constructors keyed to eType () at /usr/include/g++-3/stl_multimap.h:75 #6 0x083fb895 in __do_global_ctors_aux () at slMODfile.cxx:686 #7 0x0804e0ae in _init () at eval.c:41 #8 0x40317161 in __libc_start_main (main=0x80573ec main, argc=1, ubp_av=0xb8ec, init=0x804e098 _init, fini=0x8450e80 _fini, rtld_fini=0x4000e184 _dl_fini, stack_end=0xb8dc) at ../sysdeps/generic/libc-start.c:122 FWIW I have done things like: - uninstall SimGear and plib, and reinstalled. - I have done a cvs co from our uiuc mirror and a cvs update -dP from the fgfs site. I get the same segfault w/ both versions of the code. - As compared w/ the last version that worked, there has been
Re: [Flightgear-devel] segfault
I seem to recall having problems with crashes when starting up with the telnet interface. Well, the problem really was with subsequent attempts at starting. I'd see segfaults if the first run didn't exit normal, either through a crash or other means. At the time I had the line for the telnet interface in my .fgfsrc. Commenting it out allowed the program to start normally. I don't know if this is apropos, but you never can tell. On Wednesday 23 October 2002 11:50 pm, Michael Selig wrote: At 10/23/02, Curtis Olson wrote: Michael Selig writes: I am still getting the same segfault w/ this option. It even promptly crashes w/ ./fgfs --help i.e. I don't get the option list. Are you missing the base package some how, or pointing to the wrong directory? If I run my working old version w/o setting FG_ROOT, I get this: [221] m-selig@qtee:/home/m-seligSim/work ./flightsim-0.7.pre11/src/Main/fgfs FlightGear: Version 0.7.11pre1 Built with GNU C++ version 2.96 Scanning for root: command line fg_root = /home/m-seligSim/www-flightgear-org/fgfsbase Usage: strings/usage strings/general-options: --help, -h strings/help-desc snip For a complete list of options use --help --verbose Base package check failed ... Found version 0.9.0 at: /home/m-seligSim/www-flightgear-org/fgfsbase Please upgrade to version0.7.11pre1 When I run the new one the same way, I get this: [226] m-selig@qtee:/home/m-seligSim/www-flightgear-org ./FlightGear/src/Main/fgfs Segmentation fault So this does not seem to be related to the base package. FWIW I will not rule out that I could be making some mistakes at my end, but I have already tried working this out w/ Rob Deters here. Also, our most recent update follows the steps we have taken before ... and on Rob's computer it is working. He is running Redhat 7.2. I am running 7.1, and that's the only difference on the surface. Still puzzled in Illinois ... and trying very hard to avoid having to reinstall my wonderful Linux box. Curt. -- Curtis Olson IVLab / HumanFIRST Program FlightGear Project Twin Cities[EMAIL PROTECTED] [EMAIL PROTECTED] Minnesota http://www.menet.umn.edu/~curt http://www.flightgear.org ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] segfault
And it only happens with *some* *JSBSim* aircraft? Jon -Original Message- From: [EMAIL PROTECTED] [mailto:flightgear-devel-admin;flightgear.org]On Behalf Of Curtis L. Olson Sent: Wednesday, October 23, 2002 11:13 PM To: [EMAIL PROTECTED] Subject: RE: [Flightgear-devel] segfault I'm not coming up with any good ideas ... I *thought* that if you didn't specify --enable-clouds3d, then none of that code was executed, but perhaps that's not the case ... (?) From gdb, it's dying in the 3d cloud setup/init but beyond that I'm not sure why. Curt. Jon Berndt writes: Can anyone offer some help, here? I do not have a recent build of FlightGear and cannot build it at the moment for reasons I don't want to go into (that have nothing to do with FlightGear or my computer). Can someone copy the log output concerning JSBSim for the X-15 and post it or email to me and Tony? Also, some detailed info and wierdness and/or where it segfaults would be helpful. Platform info, too. Jon -Original Message- From: [EMAIL PROTECTED] [mailto:flightgear-devel-admin;flightgear.org]On Behalf Of Michael Selig Sent: Wednesday, October 23, 2002 10:54 PM To: [EMAIL PROTECTED] Subject: Re: [Flightgear-devel] segfault At 10/23/02, John Check wrote: I just ran through firing up all the non 172 planes and there are several JSBsim planes that segfault x24b X15 Shuttle I have been down this road before. These planes are crashing for some reason, and the segfault is not the first thing that happens. This segfault is very different and probably simply FDM related. It seems that a big clue w/ my segfault is that it happens right out of the box, i.e. immediately. On Wednesday 23 October 2002 10:30 pm, Tony Peden wrote: On Wed, 2002-10-23 at 19:14, Michael Selig wrote: At 10/23/02, Tony Peden wrote: On Wed, 2002-10-23 at 17:39, Michael Selig wrote: I am trying to compile and run the latest version of fgfs, but I have hit a problem. When I run it I promptly get the error message Segmentation Fault There are no other messages. What I have: - Redhat 7.1 - automake 1.6.3 - autoconf 2.53 - plib 1.6.0 - yesterday's cvs of Simgear, fgfsbase, Flightgear (0.9) I am able to compile and run my older version of fgfs (from 8/20/2002) w/ the new plib and Simgear. Also, we're able to compile and run the new setup on some other Redhat machines. So this does seem to be machine specific, but I have not changed anything at the system level. Anyone have any ideas on what I could try next? It may help to know where it's crashing. run fgfs with this: gdb fgfs type run at the gdb prompt then, when it crashes, type bt and post the results. Here's what I get: ~/www-flightgear-org gdb ./FlightGear/src/Main/fgfs GNU gdb 5.0rh-5 Red Hat Linux 7.1 Copyright 2001 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as i386-redhat-linux... (gdb) run Starting program: /home/m-seligSim/www-flightgear-org/./FlightGear/src/Main/fgfs [New Thread 1024 (LWP 21926)] Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 1024 (LWP 21926)] __strtol_internal (nptr=0x8833618 , endptr=0x85ccee0, base=139597448, group=1065353216) at eval.c:36 36 eval.c: No such file or directory. in eval.c (gdb) bt #0 __strtol_internal (nptr=0x8833618 , endptr=0x85ccee0, base=139597448, group=1065353216) at eval.c:36 #1 0x0834b82a in SkyTextureState::SkyTextureState (this=0x8833618) at SkyTextureState.cpp:47 #2 0x08348a5f in SkyMaterial::SkyMaterial (this=0x8833578) at SkyMaterial.cpp:60 #3 0x08348223 in SkyLight::SkyLight (this=0x8833500, eType=SKY_LIGHT_DIRECTIONAL) at SkyLight.cpp:67 #4 0x08346ce6 in __static_initialization_and_destruction_0 (__initialize_p=1, __priority=65535) at /usr/include/g++-3/stl_multimap.h:52 #5 0x08346d8e in global constructors keyed to eType () at /usr/include/g++-3/stl_multimap.h:75 #6 0x083fb895 in __do_global_ctors_aux () at slMODfile.cxx:686 #7 0x0804e0ae in _init () at eval.c:41 #8 0x40317161 in __libc_start_main (main=0x80573ec main, argc=1, ubp_av=0xb8ec, init=0x804e098 _init, fini=0x8450e80 _fini
Re: [Flightgear-devel] segfault
On Thursday 24 October 2002 12:18 am, Jon Berndt wrote: And it only happens with *some* *JSBSim* aircraft? Jon Heres console output from X15 Starting and initialitoken = OBJECT name = KHAF.btg zing JSBsim T,p,rho: 518.67, 2116Start common FDM init ...initializing position... FGJSBsim::set_Longitude: -2.13554 FGJSBsim::set_Latitude: 0.65648 cur alt (ft) = 35000 FGJSBsim::set_Altitude: 35000 lat (deg) = 37.6135 Terrain altitude: -0.00124871 ...initializing ground elevation to -0.000380607ft... ...initializing sea-level radius... lat = 37.6135 alt = 35000 ...initializing velocities... FGJSBsim::set_V_calibrated_kts: 250 ...initializing Euler angles... FGJSBsim::set_Euler_Angles: 0, 0.0074002, 5.19934 End common FDM init Segmentation fault ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] segfault
At 10/23/02, Curtis Olson wrote: I'm not coming up with any good ideas ... I *thought* that if you didn't specify --enable-clouds3d, then none of that code was executed, but perhaps that's not the case ... (?) From gdb, it's dying in the 3d cloud setup/init but beyond that I'm not sure why. Ok, given that it's in the new 3D cloud code, maybe some mods could be made so that none of that code gets executed w/ the default, which is 3D clouds off? I love to see those clouds ... but I'd be happy w/ the essentials for now. Curt. Jon Berndt writes: Can anyone offer some help, here? I do not have a recent build of FlightGear and cannot build it at the moment for reasons I don't want to go into (that have nothing to do with FlightGear or my computer). Can someone copy the log output concerning JSBSim for the X-15 and post it or email to me and Tony? Also, some detailed info and wierdness and/or where it segfaults would be helpful. Platform info, too. Jon -Original Message- From: [EMAIL PROTECTED] [mailto:flightgear-devel-admin;flightgear.org]On Behalf Of Michael Selig Sent: Wednesday, October 23, 2002 10:54 PM To: [EMAIL PROTECTED] Subject: Re: [Flightgear-devel] segfault At 10/23/02, John Check wrote: I just ran through firing up all the non 172 planes and there are several JSBsim planes that segfault x24b X15 Shuttle I have been down this road before. These planes are crashing for some reason, and the segfault is not the first thing that happens. This segfault is very different and probably simply FDM related. It seems that a big clue w/ my segfault is that it happens right out of the box, i.e. immediately. On Wednesday 23 October 2002 10:30 pm, Tony Peden wrote: On Wed, 2002-10-23 at 19:14, Michael Selig wrote: At 10/23/02, Tony Peden wrote: On Wed, 2002-10-23 at 17:39, Michael Selig wrote: I am trying to compile and run the latest version of fgfs, but I have hit a problem. When I run it I promptly get the error message Segmentation Fault There are no other messages. What I have: - Redhat 7.1 - automake 1.6.3 - autoconf 2.53 - plib 1.6.0 - yesterday's cvs of Simgear, fgfsbase, Flightgear (0.9) I am able to compile and run my older version of fgfs (from 8/20/2002) w/ the new plib and Simgear. Also, we're able to compile and run the new setup on some other Redhat machines. So this does seem to be machine specific, but I have not changed anything at the system level. Anyone have any ideas on what I could try next? It may help to know where it's crashing. run fgfs with this: gdb fgfs type run at the gdb prompt then, when it crashes, type bt and post the results. Here's what I get: ~/www-flightgear-org gdb ./FlightGear/src/Main/fgfs GNU gdb 5.0rh-5 Red Hat Linux 7.1 Copyright 2001 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as i386-redhat-linux... (gdb) run Starting program: /home/m-seligSim/www-flightgear-org/./FlightGear/src/Main/fgfs [New Thread 1024 (LWP 21926)] Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 1024 (LWP 21926)] __strtol_internal (nptr=0x8833618 , endptr=0x85ccee0, base=139597448, group=1065353216) at eval.c:36 36 eval.c: No such file or directory. in eval.c (gdb) bt #0 __strtol_internal (nptr=0x8833618 , endptr=0x85ccee0, base=139597448, group=1065353216) at eval.c:36 #1 0x0834b82a in SkyTextureState::SkyTextureState (this=0x8833618) at SkyTextureState.cpp:47 #2 0x08348a5f in SkyMaterial::SkyMaterial (this=0x8833578) at SkyMaterial.cpp:60 #3 0x08348223 in SkyLight::SkyLight (this=0x8833500, eType=SKY_LIGHT_DIRECTIONAL) at SkyLight.cpp:67 #4 0x08346ce6 in __static_initialization_and_destruction_0 (__initialize_p=1, __priority=65535) at /usr/include/g++-3/stl_multimap.h:52 #5 0x08346d8e in global constructors keyed to eType () at /usr/include/g++-3/stl_multimap.h:75 #6 0x083fb895 in __do_global_ctors_aux () at slMODfile.cxx:686 #7 0x0804e0ae in _init () at eval.c:41 #8 0x40317161 in __libc_start_main (main=0x80573ec main, argc=1, ubp_av=0xb8ec, init=0x804e098 _init, fini=0x8450e80 _fini, rtld_fini=0x4000e184 _dl_fini, stack_end=0xb8dc) at ../sysdeps/generic/libc-start.c:122 FWIW I have done things like
Re: [Flightgear-devel] segfault (linux)
Alex, Make sure you have the latest base package ... I think some default properties changed. I don't think this should lead to a segfault, but apparently it does ... Curt. Alex Perry writes: ... Cannot open file: /usr/local/lib/FlightGear/Scenery/Objects.txt Initializing splash screen Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 1024 (LWP 1748)] fgReshape (width=1024, height=768) at main.cxx:1243 1243 viewmgr-get_current_view()-get_v_fov() ); (gdb) bt #0 fgReshape (width=1024, height=768) at main.cxx:1243 #1 0x4007e245 in __glutRegisterEventParser () from /usr/lib/libglut.so.3 #2 0x4007e4ab in glutMainLoop () from /usr/lib/libglut.so.3 #3 0x08053854 in mainLoop (argc=1, argv=0xbb54) at main.cxx:1563 #4 0x0805404e in main (argc=1, argv=0xbb54) at main.cxx:1622 #5 0x4030c6cf in __libc_start_main () from /lib/libc.so.6 (gdb) print viewmgr-get_current_view()-get_v_fov() Cannot access memory at address 0x0 ... it's trying to get the parameters for the call to ssgSetFOV() ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel -- Curtis Olson IVLab / HumanFIRST Program FlightGear Project Twin Cities[EMAIL PROTECTED] [EMAIL PROTECTED] Minnesota http://www.menet.umn.edu/~curt http://www.flightgear.org ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] segfault (linux)
Yep, that apparently fixed it. Curt said: Make sure you have the latest base package ... I think some default properties changed. I don't think this should lead to a segfault, but apparently it does ... Alex Perry writes: ... Cannot open file: /usr/local/lib/FlightGear/Scenery/Objects.txt Initializing splash screen Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 1024 (LWP 1748)] fgReshape (width=1024, height=768) at main.cxx:1243 1243 viewmgr-get_current_view()-get_v_fov() ); (gdb) bt #0 fgReshape (width=1024, height=768) at main.cxx:1243 #1 0x4007e245 in __glutRegisterEventParser () from /usr/lib/libglut.so.3 #2 0x4007e4ab in glutMainLoop () from /usr/lib/libglut.so.3 #3 0x08053854 in mainLoop (argc=1, argv=0xbb54) at main.cxx:1563 #4 0x0805404e in main (argc=1, argv=0xbb54) at main.cxx:1622 #5 0x4030c6cf in __libc_start_main () from /lib/libc.so.6 (gdb) print viewmgr-get_current_view()-get_v_fov() Cannot access memory at address 0x0 ... it's trying to get the parameters for the call to ssgSetFOV() ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] segfault (linux)
Curt, The new default properties set up the various views. So the problem is if running the new code, and none is defined there would be no view to access. I'm going to submit some patches that consolidate some of the matrix math for models and views, which included some patches to the view manager. After this I've got a little more cleaning up to do in the view manager. Should I hard code a default pilot view in there (ie if none is defined)? Alternatively, if you can lead me to a graceful way of printing a message and exiting... Thanks, Jim Curt said: Make sure you have the latest base package ... I think some default properties changed. I don't think this should lead to a segfault, but apparently it does ... ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] segfault on mini-panels
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], etc. and allow 's' to cycle through the whole list. All the best, David -- David Megginson [EMAIL PROTECTED] ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] segfault on mini-panels
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 property; instead, we should have panel[0], panel[1], panel[2], etc. and allow 's' to cycle through the whole list. 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 which branch is active. This might be a useful thing to do with views as well. Best, Jim ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] segfault on mini-panels
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 ago; but the viewport window was the wrong size so that shrinking the panel didn't make much extra scenery visible. ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] segfault on mini-panels
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::~FGComparisonCondition ( this=0x95e9850, __in_chrg=3) at fg_props.cxx:1007 #3 0x806b39d in FGAndCondition::~FGAndCondition (this=0x97156c0, __in_chrg=3) at fg_props.cxx:859 #4 0x806d128 in FGConditional::~FGConditional (this=0x9747f50, __in_chrg=3) at fg_props.cxx:1163 #5 0x80b4f18 in FGInstrumentLayer::~FGInstrumentLayer (this=0x9747f50, __in_chrg=3) at panel.cxx:848 #6 0x80b52e1 in FGTexturedLayer::~FGTexturedLayer (this=0x9747f50, __in_chrg=3) at panel.cxx:939 #7 0x80b4b64 in FGLayeredInstrument::~FGLayeredInstrument (this=0x9747f18, __in_chrg=3) at panel.cxx:781 #8 0x80b2ac4 in FGPanel::~FGPanel (this=0x8f86838, __in_chrg=3) at panel.cxx:199 #9 0x80581fc in do_panel_load (arg=0x922c2d0, state=0x922c2c8) at fg_commands.cxx:209 #10 0x82b5105 in FGBinding::fire (this=0x922c2b0) at input.cxx:138 #11 0x82b551f in FGInput::doKey (this=0x8566300, k=115, modifiers=0, x=301, y=-10) at input.cxx:246 #12 0x82b7961 in GLUTkey (k=115, x=301, y=-10) at input.cxx:724 #13 0x400822aa in processEventsAndTimeouts () from /usr/X11R6/lib/libglut.so.3 Alex Perry [EMAIL PROTECTED] said: 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 ago; but the viewport window was the wrong size so that shrinking the panel didn't make much extra scenery visible. ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] segfault on mini-panels
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 getting them after the prop's changed but I hadn't updated for a day or two Norman ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
