Bug 577492 - [abrt] crash in FlightGear-2.0.0-1.fc13: Process /usr/bin/fgfs was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in FlightGear-2.0.0-1.fc13: Process /usr/bin/fgfs was killed by ...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: FlightGear
Version: 13
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Fabrice Bellet
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:6e9160f1da41109d7efe9807cc8...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-03-27 13:33 UTC by Elad Alfassa
Modified: 2010-06-18 10:42 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-06-08 08:04:01 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (13.08 KB, text/plain)
2010-03-27 13:33 UTC, Elad Alfassa
no flags Details

Description Elad Alfassa 2010-03-27 13:33:31 UTC
abrt 1.0.8 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: fgfs
component: FlightGear
executable: /usr/bin/fgfs
kernel: 2.6.33.1-19.fc13.x86_64
package: FlightGear-2.0.0-1.fc13
rating: 4
reason: Process /usr/bin/fgfs was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)

How to reproduce
-----
1.Start FlightGear
2.Wait a few seconds
3.It crashes :-(

Comment 1 Elad Alfassa 2010-03-27 13:33:34 UTC
Created attachment 403006 [details]
File: backtrace

Comment 2 Elad Alfassa 2010-03-27 13:34:18 UTC

How to reproduce
-----
1.Start FlightGear
2.Wait a few seconds
3.It crashes :-(

Comment 3 Fabrice Bellet 2010-03-27 17:51:05 UTC
I cannot reproduce the bug myself. Do you start FlightGear from the menu or from the command-line with specific options ? Do you have some specific startup options ? Is the crash always reproducible ?

If you wish to do some further debugging, could you eventually reproduce the bug while running the program under the gdb debugger ? and then report some variable values, for example :

(gdb) print groundLights0
$1 = (osg::Group *) 0xad6983a0
(gdb) print lightManager
$2 = (simgear::GroundLightManager *) 0x858f630
(gdb) print *lightManager
$3 = {<simgear::ReferencedSingleton<simgear::GroundLightManager>> = {
    <osg::Referenced> = {_vptr.Referenced = 0xb6d7c4, _observerSetDataPtr = {
        _ptr = 0x0}, _refCount = {_value = 1}}, 
    _vptr.ReferencedSingleton = 0xb6d7ac}, runwayLightSS = {_ptr = 0x858f650}, 
  taxiLightSS = {_ptr = 0x858f780}, groundLightSS = {_ptr = 0x858f8c0}}
(gdb) 

Thanks in advance!

Comment 4 clifford snow 2010-04-06 23:09:26 UTC
I'm experiencing the same problem.  FlightGear has a segmentation fault when run /usr/bin/fgfs or with parameters such as
/usr/bin/fgfs --atlas=socket,out,1,localhost,$PORT,udp $*

It was working until I started using a joystick.  

Debug of core gave incomplete information.  What I have is
Reading symbols from /usr/bin/fgfs...Reading symbols from /usr/lib/debug/usr/bin/fgfs.debug...
warning: section .dynbss not found in /usr/lib/debug/usr/bin/fgfs.debug
done.
done.
[New Thread 5626]
[New Thread 5639]
[New Thread 5622]
[New Thread 5624]

warning: section .dynbss not found in /usr/lib/debug/usr/bin/fgfs.debug
Missing separate debuginfo for 
Try: yum --disablerepo='*' --enablerepo='*-debuginfo' install /usr/lib/debug/.build-id/d5/10cefba00203567a1e982d3e08fb9f670a463b
Reading symbols from /lib64/ld-linux-x86-64.so.2...(no debugging symbols found)...done.
Loaded symbols for /lib64/ld-linux-x86-64.so.2

warning: section .dynbss not found in /usr/lib/debug/usr/bin/fgfs.debug
Core was generated by `/usr/bin/fgfs --atlas=socket,out,1,localhost,5500,udp'.
Program terminated with signal 11, Segmentation fault.
#0  0x00000039c7221015 in ?? ()
Missing separate debuginfos, use: debuginfo-install OpenSceneGraph-libs-2.8.2-3.fc12.x86_64 OpenThreads-2.8.2-3.fc12.x86_64 SimGear-2.0.0-1.fc14.x86_64 dbus-libs-1.2.16-9.fc12.x86_64 expat-2.0.1-8.fc12.x86_64 freealut-1.1.0-11.fc12.x86_64 freeglut-2.6.0-1.fc12.x86_64 glibc-2.11.1-1.x86_64 libFLAC8-1.2.1-1_14.fc8_90.x86_64 libICE-1.0.6-1.fc12.x86_64 libSM-1.1.0-7.fc12.x86_64 libX11-1.3-1.fc12.x86_64 libXau-1.0.5-1.fc12.x86_64 libXdamage-1.1.2-1.fc12.x86_64 libXext-1.1-2.fc12.x86_64 libXfixes-4.0.4-1.fc12.x86_64 libXi-1.3-2.fc12.x86_64 libXrandr-1.3.0-5.fc12.x86_64 libXrender-0.9.5-1.fc12.x86_64 libXtst-1.0.99.2-3.fc12.x86_64 libXxf86vm-1.1.0-1.fc12.x86_64 libasyncns-0.8-1.fc12.x86_64 libcap-ng-0.6.2-3.fc12.x86_64 libdrm-2.4.17-1.fc12.x86_64 libgcc-4.4.3-4.fc12.x86_64 libjpeg-6b-46.fc12.x86_64 libogg-1.1.4-2.fc12.x86_64 libpng-1.2.43-1.fc12.x86_64 libselinux-2.0.90-5.fc12.x86_64 libsndfile-1.0.20-3.fc12.x86_64 libstdc++-4.4.3-4.fc12.x86_64 libuuid-2.16.2-7.fc12.x86_64 libvorbis-1.2.3-4.fc12.x86_64 libxcb-1.5-1.fc12.x86_64 mesa-dri-drivers-7.7-4.fc12.x86_64 mesa-libGL-7.7-4.fc12.x86_64 mesa-libGLU-7.7-4.fc12.x86_64 openal-soft-1.11.753-3.20100225git.fc12.x86_64 plib-1.8.5-3.fc12.x86_64 pulseaudio-libs-0.9.21-5.fc12.x86_64 tcp_wrappers-libs-7.6-56.fc12.x86_64 zlib-1.2.3-23.fc12.x86_64

Comment 5 clifford snow 2010-04-12 01:58:40 UTC
I think the problem was solved by removing all of the Scenery files from both /usr/share/FlightGear/Scenery and ~/.fgfs/Scenery then a complete remove and reinstall of FlightGear.  I noticed that FlightGear crashed loading the Scenery Objects.  The .fgfs/Scenery had thousands of files.

Comment 6 clifford snow 2010-04-13 23:08:04 UTC
OK I was wrong.  After rebooting, FlightGear gave the same segmentation fault.  I removed and reinstalled FlightGear from downloaded RPMs.  It works just fine, apparently until I reboot.  That doesn't make sense to me.  It apparently doesn't have anything to do with the Scenery files.

Comment 7 clifford snow 2010-04-18 17:24:30 UTC
I ran a backtrace and received the follow


#0  0x000000391b421015 in SGLoadBTG(std::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, SGMaterialLib*, bool, bool, bool) ()
   from /usr/lib64/libsgtgdb-2.0.0.so
#1  0x000000391b4357c3 in SGReaderWriterBTG::readNode(std::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, osgDB::ReaderWriter::Options const*) const () from /usr/lib64/libsgtgdb-2.0.0.so
#2  0x000000391b435fbf in simgear::ModelRegistryCallback<simgear::DefaultProcessPolicy, simgear::NoCachePolicy, simgear::NoOptimizePolicy, simgear::NoSubstitutePolicy, simgear::BuildGroupBVHPolicy>::loadUsingReaderWriter(std::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, osgDB::ReaderWriter::Options const*) () from /usr/lib64/libsgtgdb-2.0.0.so
#3  0x000000391b43635e in simgear::ModelRegistryCallback<simgear::DefaultProcessPolicy, simgear::NoCachePolicy, simgear::NoOptimizePolicy, simgear::NoSubstitutePolicy, simgear::BuildGroupBVHPolicy>::readNode(std::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, osgDB::ReaderWriter::Options const*) () from /usr/lib64/libsgtgdb-2.0.0.so
#4  0x000000391c47748e in simgear::ModelRegistry::readNode(std::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, osgDB::ReaderWriter::Options const*) () from /usr/lib64/libsgmodel-2.0.0.so
#5  0x0000003917a54eb9 in readNode (filename=
    "/usr/share/FlightGear/Scenery/Terrain/w130n30/w123n37/942058.btg", 
    options=0x7f87081519b0)
    at /usr/src/debug/OpenSceneGraph-2.8.2/OpenSceneGraph-2.8.2/include/osgDB/Re---Type <return> to continue, or q <return> to quit---
gistry:237
#6  osgDB::readNodeFile (filename=
    "/usr/share/FlightGear/Scenery/Terrain/w130n30/w123n37/942058.btg", 
    options=0x7f87081519b0)
    at /usr/src/debug/OpenSceneGraph-2.8.2/OpenSceneGraph-2.8.2/src/osgDB/ReadFile.cpp:69
#7  0x000000391b43c569 in simgear::TileEntry::obj_load(std::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, osg::Group*, bool, osgDB::ReaderWriter::Options const*) () from /usr/lib64/libsgtgdb-2.0.0.so
#8  0x000000391b43d7f4 in simgear::TileEntry::loadTileByFileName(std::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, osgDB::ReaderWriter::Options const*) () from /usr/lib64/libsgtgdb-2.0.0.so
#9  0x000000391b432f9f in simgear::ReaderWriterSTG::readNode(std::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, osgDB::ReaderWriter::Options const*) const () from /usr/lib64/libsgtgdb-2.0.0.so
#10 0x000000391b44159f in simgear::ModelRegistryCallback<simgear::DefaultProcessPolicy, simgear::NoCachePolicy, simgear::NoOptimizePolicy, simgear::NoSubstitutePolicy, simgear::BuildLeafBVHPolicy>::loadUsingReaderWriter(std::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, osgDB::ReaderWriter::Options const*) () from /usr/lib64/libsgtgdb-2.0.0.so
#11 0x000000391b4416c4 in simgear::ModelRegistryCallback<simgear::DefaultProcessPolicy, simgear::NoCachePolicy, simgear::NoOptimizePolicy, simgear::NoSubstitutePolicy, simgear::BuildLeafBVHPolicy>::readNode(std::basic_string<char, std::char---Type <return> to continue, or q <return> to quit---
_traits<char>, std::allocator<char> > const&, osgDB::ReaderWriter::Options const*) () from /usr/lib64/libsgtgdb-2.0.0.so
#12 0x000000391c47748e in simgear::ModelRegistry::readNode(std::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, osgDB::ReaderWriter::Options const*) () from /usr/lib64/libsgmodel-2.0.0.so
#13 0x0000003917a336d6 in readNode (this=0x196fdd0)
    at /usr/src/debug/OpenSceneGraph-2.8.2/OpenSceneGraph-2.8.2/include/osgDB/Registry:237
#14 osgDB::DatabasePager::DatabaseThread::run (this=0x196fdd0)
    at /usr/src/debug/OpenSceneGraph-2.8.2/OpenSceneGraph-2.8.2/src/osgDB/DatabasePager.cpp:551
#15 0x0000003bdc604989 in OpenThreads::ThreadPrivateActions::StartThread (
    data=<value optimized out>)
    at /usr/src/debug/OpenSceneGraph-2.8.2/OpenSceneGraph-2.8.2/src/OpenThreads/pthreads/PThread.c++:167
#16 0x0000003bdba06a3a in start_thread (arg=0x7f870e298710)
    at pthread_create.c:297
#17 0x0000003bdaede65d in clone ()
    at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#18 0x0000000000000000 in ?? ()

Comment 8 Fabrice Bellet 2010-04-26 14:25:03 UTC
(In reply to comment #4)

> 
> It was working until I started using a joystick.  
> 

Can you test if the crash is related to presence of the joystick ? Does it work is you unplug it ? I found another similar crash report, that indicates that the problem appeared after adding a joystick too :  http://www.flightgear.org/forums/viewtopic.php?f=20&p=75450

Comment 9 clifford snow 2010-04-27 21:53:32 UTC
It doesn't appear to be related to the joystick.  It crashes without the joystick.

Last night I added FlightGear to the prelink blacklist.  Today FlightGear is still working without reinstalling.  I will check the next few days to see if this solves the problem.  

I added FlightGear.conf to /etc/prelink.conf.d

FlightGear.conf contains the following line:
-b /usr/bin/fgfs

Comment 10 Fabrice Bellet 2010-04-28 21:01:10 UTC
yes! I confirm this is related to prelink. Congratulation for finding the trigger of the problem. I finally could reproduce the crash. The good news is that the bug has been fixed in glibc-2.11.90-17, without requiring to blacklist fgfs from prelink.

Comment 11 Fabrice Bellet 2010-06-08 08:04:01 UTC
closing this bug, as the newer glibc fixed the problem.

Comment 12 Marek Zdunek 2010-06-18 10:42:52 UTC
problem still exists

Package:    	FlightGear-2.0.0-1.fc13
Latest Crash:	pią, 18 cze 2010, 12:39:32
Command:    	fgfs
Reason:     	Process /usr/bin/fgfs was killed by signal 11 (SIGSEGV)

$ fgfs
Error: Not able to create requested visual.
Error: Not able to create requested visual.
Naruszenie ochrony pamięci (core dumped)

$ uname -a
Linux amd64 2.6.33.5-124.fc13.x86_64 #1 SMP Fri Jun 11 09:38:12 UTC 2010 x86_64 x86_64 x86_64 GNU/Linux

$ yum list glibc
Zainstalowane pakiety
glibc.i686                                                                    2.12-2                                                                  @updates
glibc.x86_64                                                                  2.12-2                                                                  @updates


Note You need to log in before you can comment on or make changes to this bug.