Bug 1007518

Summary: [abrt] supertux-0.3.3-11.fc19: atomic_increment: Process /usr/bin/supertux2 was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: javier del cristo <javlopez22>
Component: supertuxAssignee: David King <amigadave>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 19CC: samuel-rhbugs, steve, wangjiezhe
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:e87093d96d47c55af4e0e80db08701ab19374084
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-11-11 22:54:43 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description javier del cristo 2013-09-12 16:19:14 UTC 
Description of problem:
The bug always occurs when turn off of program, but apparently when it is running is executed correctly, the problem is at the moment down out

Version-Release number of selected component:
supertux-0.3.3-11.fc19

Additional info:
reporter:       libreport-2.1.6
backtrace_rating: 4
cmdline:        supertux2
crash_function: atomic_increment
executable:     /usr/bin/supertux2
kernel:         3.10.10-200.fc19.x86_64
runlevel:       N 5
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 atomic_increment at /usr/include/boost/smart_ptr/detail/sp_counted_base_gcc_x86.hpp:66
 #1 add_ref_copy at /usr/include/boost/smart_ptr/detail/sp_counted_base_gcc_x86.hpp:134
 #2 shared_count at /usr/include/boost/smart_ptr/detail/shared_count.hpp:382
 #3 shared_ptr at /usr/include/boost/smart_ptr/shared_ptr.hpp:328
 #4 PlayerStatus::draw at /usr/src/debug/supertux-0.3.3/src/supertux/player_status.cpp:160
 #5 GameSession::drawstatus at /usr/src/debug/supertux-0.3.3/src/supertux/game_session.cpp:591
 #6 GameSession::draw at /usr/src/debug/supertux-0.3.3/src/supertux/game_session.cpp:369
 #7 ScreenManager::draw at /usr/src/debug/supertux-0.3.3/src/supertux/screen_manager.cpp:145
 #8 ScreenManager::run at /usr/src/debug/supertux-0.3.3/src/supertux/screen_manager.cpp:326
 #9 Main::run at /usr/src/debug/supertux-0.3.3/src/supertux/main.cpp:629

Potential duplicate: bug 728805
Comment 1 javier del cristo 2013-09-12 16:19:22 UTC 
Created attachment 796937 [details]
File: backtrace
Comment 2 javier del cristo 2013-09-12 16:19:30 UTC 
Created attachment 796938 [details]
File: cgroup
Comment 3 javier del cristo 2013-09-12 16:19:34 UTC 
Created attachment 796939 [details]
File: core_backtrace
Comment 4 javier del cristo 2013-09-12 16:19:39 UTC 
Created attachment 796940 [details]
File: dso_list
Comment 5 javier del cristo 2013-09-12 16:19:46 UTC 
Created attachment 796941 [details]
File: environ
Comment 6 javier del cristo 2013-09-12 16:19:49 UTC 
Created attachment 796942 [details]
File: limits
Comment 7 javier del cristo 2013-09-12 16:20:01 UTC 
Created attachment 796943 [details]
File: maps
Comment 8 javier del cristo 2013-09-12 16:20:07 UTC 
Created attachment 796944 [details]
File: open_fds
Comment 9 javier del cristo 2013-09-12 16:20:14 UTC 
Created attachment 796945 [details]
File: proc_pid_status
Comment 10 javier del cristo 2013-09-12 16:20:40 UTC 
Created attachment 796946 [details]
File: var_log_messages
Comment 11 Fedora Admin XMLRPC Client 2014-11-10 15:32:38 UTC 
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.
Comment 12 Fedora Admin XMLRPC Client 2014-11-11 08:30:55 UTC 
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.
Comment 13 David King 2014-11-11 22:54:43 UTC 

*** This bug has been marked as a duplicate of bug 1162883 ***