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
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
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
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, > > > > >
Re: [Flightgear-devel] ***long*** pauses after flying a while
On Wednesday 23 October 2002 11:48 pm, Curtis L. Olson wrote: > I just fixed a bug in the tile freeing code which accounted for the > very long pauses people were seeing after flying for a while. Cool, but it breaks for gcc3.2 line 704 of tileentry.cxx needs std::cout ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
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 > > 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
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 , argc=1, > > >
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 , 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
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 , 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 > > > > > > > > > >
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 , 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 P
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 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] ***long*** pauses after flying a while
I just fixed a bug in the tile freeing code which accounted for the very long pauses people were seeing after flying for a while. After a while the tile cache fills up and the oldest entries need to be purged. The problem is that to free an entire tile takes mroe that a frame's worth of time so we split it up over multiple frames so in theory you don't see a fps hit. However, there was a bug in the code that did the partial tile deletion and it could leave an partial tree when it was done. I had a fail safe to catch this so there was never a memory leak [with this] but if the fail safe kicked in and the left over portion of the tree was large, it could really nail you for a big pause. That should be fixe now. However there is still an issue to worry about. The random ground cover code can create thousands of objects which means a branch node in our scene graph with thousands of kids. plib is not exactly efficient at deleting kids and even if you know the index, it converts this to a pointer and then later needs to do a linear search to find the index again. I've submitted a patch to the plib list to help with this, but I've never had good luck getting any plib code to change. Even so, 4000 children of a single branch node is a *lot* and since plib uses linear array list structures, deleting a child will never be fast even after removing the unnecessary linear search. I don't know if there's anything we can do about our own scene graph structure at the moment ... perhaps we could introduce a new level of branches (one per strip/fan) ? That wouldn't reduce the number of ground cover objects, but if we can keep the lists smaller that would keeps us away from needing to delete one child out of 4000, then one out 3999, then one out of 3998, etc. ... So currently when you free one of these nightmare tiles, the frame rates can get chuncky, but you won't get that really big hit any more. This situation could be improved with my suggested patch to plib if someone over there applies it. This could further be improved if we find a way to restructure our random ground cover objects section of the scene graph to avoid these really *huge* kid list sizes. 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
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 , 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 [EMA
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
[Flightgear-devel] FlightGear 0.8.0 on Win98SE
Hi, First things first ... very impressive work, congratulations !!! Then ... I tried your 0.8.0 binary distribution on a AMD Athlon/1333 with 384MB RAM and GeForce2 PRO/32MB machine running Win98SE/Polish. Here is a brief "report" ... The "fgfs.exe" runs well (on a couple of occasions the sound stopped, and I had to "kill" it twice yesterday, however). Both the "fgjs.exe" and the "js_demo.exe" die immediately after I try to run them (some kind of a "general protection error" + "registers dump"). The "gl-info.exe" refuses to start with a note that "cygwin" dll is missing (which is correct, I do not have "cygwin" installed - the manual does not require it for the binary win32 distribution). I have two USB Logitech WingMan RumblePads connected. They were not recognized by default. I would like to ask the one who is responsible for : /FlightGear/Input/Joysticks/Logitech/wingman-rumblepad-usb.xml to add the following line into it : Logitech WingMan RumblePad USB (The recent RumblePad driver seems to define the name this way.) There are two problems with the joystick. First, there are two vertical "bars/arrows" in the cockpit for the "elevators", but only the "right" one is following the joystick (the "left" one always stays in the middle) - however, if I "view" the plane from "outside" I can see that both (left and right) are moving up/down. Second - both the "aileron" and "elevator" quite often misbehave - what I observe is that when I move them then appropriate "bars/arrows" are also moving, but every now and then the "bars/arrows" suddenly jump to the "neutral" position (and so they quite often jump between the "actual" joystick position and the "neutral" position). This can also be seen when I "view" the plane from "outside" - indeed "ailerons" and "elevators" are jumping - this makes the steering quite difficult. I monitored the joystick with an external utility and this utility does not show such problems, so it must be the "software". I did not observe such problems with the "rudder", but ... maybe it is just the "lack of experience". There is also another "annoying" problem. Basically, the FGFS runs very smoothly on my machine except that every now and then (I don't have my machine at hand now, but let's say it is about every 30 seconds) it "stops" for a moment - I can see that in these moments there are always a couple of lines written on the "terminal window" - among them there is "... recalculating the sun position ...". Best regards, Jacek. P.S. Note that I'm not subscribed ... . Jacek. ___ 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 , 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 __
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 , 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 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 , 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 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
[Flightgear-devel] segfault
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? Regards, Michael ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] Generic systems
Curt sent me a generic-electrical.xml that I'll be committing shortly. In the interest of tidyness I'm considering adding a directory Aircraft/Generic to hold stuff like this. I'm not planning on moving anything like instruments in there, but possibly things like the mini panel. Basically, it would be a place for markup that would best be customized versions for a given plane, but said customized versions have yet to be written. Comments? Questions? ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] dc3 pannel lights
On Wednesday 23 October 2002 8:10 am, Curtis L. Olson wrote: > John Check writes: > > Well, Ideally, no, but like anything else, unless we have some > > documentation to work from, getting it right isn't likely. I don't know > > what doco is available. My feeling is that that we should at least have > > the > > battery and/or > > alternator connected to a main buss, which is simpler than what the 172 > > has. All we need is for a generic_electrical.xml to be loaded when one > > isn't specified. I have no problems with making it a requirement to add > > one to the markup for a plane, but I'm sure others may feel differently. > > I have no idea how this was handled prior. > > John, > > That might be the best way to go, build a super simple electrical > system that has battery, alternator feed into a single master bus, and > have all the outputs feed off that. This would probably be better > than putting in a C172 electrical system into an A4 or a 747. At some > point if someone cares, they could research the electrical system of > the specific aircraft and impliment it then. > > I don't know how much time I'll have today, but I can try to take a > quick look at this at some point, unless you want to knock it out. > > Regards, > > Curt. I'll bang one out ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] dc3 pannel lights
[EMAIL PROTECTED] writes: > Agreed. Instruments that test whether they are powered should > default to "powered" if the aircraft does not provide a suitable > electrical system. This could translate to "if the required power > bus property is not present". A simple default electrical system > that provides just a "main bus" would only satisfy instruments that > connect _directly_ to the main bus. I know that David disagrees with me on some of this, but my view is that the electrical system should provide common named outputs. For instance, panel lights would always check /systems/electrical/outputs/panel-light-power or something like that. That way the panel lights code doesn't need to know anything about how an electrical system is put together. None of the code or instruments would care if nav1 plugs into "master bus 1" on one aircraft and "critical systems bus" on another aircraft and is directly wired to the battery on a 3rd aircraft, we can easily use the same instrument and code for all of them. It's possible to parameterize the navcom (and any other) instruments so the higher level instrument panel xml file can tell each instrument where to look for it's power. But, it's harder to parameterize internal code this way. Ultimately it's 6 of one, half dozen of the other though and amounts to where you draw the line between the electrical system and the instrument panel and the rest of the code. I.e. a lot of instruments have circuit breakers or fuses between them and their power feed. The electrical system could easily model these, the panel/instruments themselves could also model their own circuit breakers and fuses. Where do you draw the dividing line? Some of this is up to the person that defines the electrical system and the instruments/panel for a particalar aircraft, but for internal code which isn't as flexible, I think some conventions need to be agreed upon. For instance, there is code that generates morse code sounds for the radios when they are properly tuned in and the ident switch is on. This is separate code from the navcom instrument panel xml, but it also needs to know where the navcom power is comming from ... we don't want to be playing morse code when the the avionics master switch is off ... especially if the panel instrument is dark. Personally I prefer to define a bunch of common, agreed upon, standard named outputs, and have the electrical system (whatever structure it has) power them. This makes defining the electrical system a bit more complex, but makes it easier and more convenient to model inline switches, circuit breakers, and fuses, especially if we are connecting this to real cockpit hardware that has these sorts of things. My 2 cents ... 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] dc3 pannel lights
Andy Ross wrote: > > John Check wrote: > > What it is is that when electrical system modeling was added it > > affected planes for which no electrical system was added. > > Shouldn't the sane choice for the defaults be the opposite? The > instruments work unless the electrical system tells them that they are > disabled? Agreed. Instruments that test whether they are powered should default to "powered" if the aircraft does not provide a suitable electrical system. This could translate to "if the required power bus property is not present". A simple default electrical system that provides just a "main bus" would only satisfy instruments that connect _directly_ to the main bus. - Julian ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] --enable-auto-coordination
At 10/23/02, Erik Hofman wrote: Michael Selig wrote: I have a few models that run w/ the --enable-auto-coordination flag in the startup command line. Is there a way to do this in the *-set.xml file instead? If it is possible, I'd like to make such a change w/ my Wright Flyer model on the cvs. Just add: true Erik Thanks! ___ 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] --enable-auto-coordination
Michael Selig wrote: I have a few models that run w/ the --enable-auto-coordination flag in the startup command line. Is there a way to do this in the *-set.xml file instead? If it is possible, I'd like to make such a change w/ my Wright Flyer model on the cvs. Just add: true Erik ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] --enable-auto-coordination
I have a few models that run w/ the --enable-auto-coordination flag in the startup command line. Is there a way to do this in the *-set.xml file instead? If it is possible, I'd like to make such a change w/ my Wright Flyer model on the cvs. Thanks, Michael ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] KOAK lighting
On Tuesday 22 October 2002 06:45 pm, John Check wrote: > Is KOAK the only thing that changed in that tarball? It should have been. Wm -- William L. Riley [EMAIL PROTECTED] ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] dc3 pannel lights
John Check writes: > Well, Ideally, no, but like anything else, unless we have some documentation > to work from, getting it right isn't likely. I don't know what doco is > available. My feeling is that that we should at least have the > battery and/or > alternator connected to a main buss, which is simpler than what the 172 has. > All we need is for a generic_electrical.xml to be loaded when one isn't > specified. I have no problems with making it a requirement to add one to the > markup for a plane, but I'm sure others may feel differently. > I have no idea how this was handled prior. John, That might be the best way to go, build a super simple electrical system that has battery, alternator feed into a single master bus, and have all the outputs feed off that. This would probably be better than putting in a C172 electrical system into an A4 or a 747. At some point if someone cares, they could research the electrical system of the specific aircraft and impliment it then. I don't know how much time I'll have today, but I can try to take a quick look at this at some point, unless you want to knock it out. 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
