Red Hat Bugzilla – Bug 967105
[abrt] supertuxkart-0.7.3-1.fc18: _M_grab: Process /usr/bin/supertuxkart was killed by signal 11 (SIGSEGV)
Last modified: 2014-01-11 01:36:00 EST
Description of problem:
I was starting SuperTuxKart with two USB gamepads connected (2x Logitech Gamepad F310), and I only pressed the A (fire) button a few times.
Version-Release number of selected component:
cmdline: supertuxkart --log=file
Thread no. 1 (10 frames)
#0 _M_grab at /usr/src/debug/gcc-4.7.2-20121109/obj-x86_64-redhat-linux/x86_64-redhat-linux/libstdc++-v3/include/bits/basic_string.h:226
#1 std::basic_string<char, std::char_traits<char>, std::allocator<char> >::basic_string at /usr/src/debug/gcc-4.7.2-20121109/obj-x86_64-redhat-linux/x86_64-redhat-linux/libstdc++-v3/include/bits/basic_string.tcc:175
#2 _Construct<std::basic_string<char>, std::basic_string<char> > at /usr/include/c++/4.7.1/bits/stl_construct.h:85
#3 __uninit_copy<__gnu_cxx::__normal_iterator<std::basic_string<char> const*, std::vector<std::basic_string<char> > >, std::basic_string<char>*> at /usr/include/c++/4.7.1/bits/stl_uninitialized.h:77
#4 uninitialized_copy<__gnu_cxx::__normal_iterator<std::basic_string<char> const*, std::vector<std::basic_string<char> > >, std::basic_string<char>*> at /usr/include/c++/4.7.1/bits/stl_uninitialized.h:119
#5 __uninitialized_copy_a<__gnu_cxx::__normal_iterator<std::basic_string<char> const*, std::vector<std::basic_string<char> > >, std::basic_string<char>*, std::basic_string<char> > at /usr/include/c++/4.7.1/bits/stl_uninitialized.h:260
#6 vector at /usr/include/c++/4.7.1/bits/stl_vector.h:310
#7 TracksScreen::init at states_screens/tracks_screen.cpp:228
#8 GUIEngine::AbstractStateManager::pushScreen at guiengine/abstract_state_manager.cpp:132
#9 GUIEngine::EventHandler::sendEventToUser at guiengine/event_handler.cpp:587
Created attachment 752809 [details]
Created attachment 752810 [details]
Created attachment 752811 [details]
Created attachment 752812 [details]
Created attachment 752813 [details]
Created attachment 752814 [details]
Created attachment 752815 [details]
Created attachment 752816 [details]
Created attachment 752817 [details]
Created attachment 752818 [details]
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '18'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 18's end of life.
Thank you for reporting this issue and we are sorry that we may not be
able to fix it before Fedora 18 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior to Fedora 18's end of life.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.