Bug 875510

Summary: [abrt] bzflag-2.4.0-4.fc17: dying: Process /usr/bin/bzflag was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: michealPW <mwalls1984>
Component: bzflagAssignee: Nils Philippsen <nphilipp>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 17CC: jeff, nphilipp, rhbugs
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:6ad9450dd0e3d74f2182fc515829725937255122
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-08-01 05:52:44 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: core_backtrace
none
File: environ
none
File: limits
none
File: backtrace
none
File: cgroup
none
File: smolt_data
none
File: maps
none
File: dso_list
none
File: proc_pid_status
none
File: open_fds
none
File: var_log_messages none

Description michealPW 2012-11-11 19:36:47 UTC
Description of problem:
My kids play bzflag with a basic configuration except for the use of an XBox Controller, using the xpad driver.

Version-Release number of selected component:
bzflag-2.4.0-4.fc17

Additional info:
libreport version: 2.0.16
abrt_version:   2.0.16
backtrace_rating: 4
cmdline:        bzflag mattyMan:mAtTy123.1.1:5154 -solo 2 -team blue
crash_function: dying
kernel:         3.6.3-1.fc17.i686

truncated backtrace:
:Thread no. 1 (8 frames)
: #2 dying at playing.cxx:504
: #4 WorldBuilder::unpack at WorldBuilder.cxx:110
: #5 loadCachedWorld at playing.cxx:1605
: #6 WorldDownLoader::start at playing.cxx:1643
: #7 handleServerMessage at playing.cxx:1903
: #8 doMessages at playing.cxx:3136
: #9 playingLoop at playing.cxx:6364
: #10 startPlaying at playing.cxx:7264

Comment 1 michealPW 2012-11-11 19:36:50 UTC
Created attachment 642995 [details]
File: core_backtrace

Comment 2 michealPW 2012-11-11 19:36:51 UTC
Created attachment 642996 [details]
File: environ

Comment 3 michealPW 2012-11-11 19:36:53 UTC
Created attachment 642997 [details]
File: limits

Comment 4 michealPW 2012-11-11 19:36:56 UTC
Created attachment 642998 [details]
File: backtrace

Comment 5 michealPW 2012-11-11 19:36:57 UTC
Created attachment 642999 [details]
File: cgroup

Comment 6 michealPW 2012-11-11 19:36:59 UTC
Created attachment 643000 [details]
File: smolt_data

Comment 7 michealPW 2012-11-11 19:37:01 UTC
Created attachment 643001 [details]
File: maps

Comment 8 michealPW 2012-11-11 19:37:02 UTC
Created attachment 643002 [details]
File: dso_list

Comment 9 michealPW 2012-11-11 19:37:04 UTC
Created attachment 643003 [details]
File: proc_pid_status

Comment 10 michealPW 2012-11-11 19:37:06 UTC
Created attachment 643004 [details]
File: open_fds

Comment 11 michealPW 2012-11-11 19:37:07 UTC
Created attachment 643005 [details]
File: var_log_messages

Comment 12 Fedora End Of Life 2013-07-04 01:27:19 UTC
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. 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 '17'.

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 17's end of life.

Bug Reporter:  Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 17 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 17'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.

Comment 13 Fedora End Of Life 2013-08-01 05:52:48 UTC
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.