Bug 1076316

Summary: [abrt] sumwars: sumwars killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Joseph O Morrow <josephomorrow>
Component: sumwarsAssignee: Martin Preisler <mpreisle>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: josephomorrow, mpreisle
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/dee1771914bb23a7ee7ade138d99401b1580e864
Whiteboard: abrt_hash:3a20808adb0f64c25a15e2baee641f76510c4b62
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-06-29 19:27:25 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: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: exploitable
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Joseph O Morrow 2014-03-14 04:27:11 UTC
Version-Release number of selected component:
sumwars-0.5.6-16.fc20

Additional info:
reporter:       libreport-2.2.0
backtrace_rating: 4
cmdline:        /usr/bin/sumwars
executable:     /usr/bin/sumwars
kernel:         3.13.5-202.fc20.i686+PAE
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (0 frames)

Comment 1 Joseph O Morrow 2014-03-14 04:27:15 UTC
Created attachment 874225 [details]
File: backtrace

Comment 2 Joseph O Morrow 2014-03-14 04:27:16 UTC
Created attachment 874226 [details]
File: cgroup

Comment 3 Joseph O Morrow 2014-03-14 04:27:18 UTC
Created attachment 874227 [details]
File: core_backtrace

Comment 4 Joseph O Morrow 2014-03-14 04:27:19 UTC
Created attachment 874228 [details]
File: dso_list

Comment 5 Joseph O Morrow 2014-03-14 04:27:21 UTC
Created attachment 874229 [details]
File: environ

Comment 6 Joseph O Morrow 2014-03-14 04:27:22 UTC
Created attachment 874230 [details]
File: exploitable

Comment 7 Joseph O Morrow 2014-03-14 04:27:24 UTC
Created attachment 874231 [details]
File: limits

Comment 8 Joseph O Morrow 2014-03-14 04:27:26 UTC
Created attachment 874232 [details]
File: maps

Comment 9 Joseph O Morrow 2014-03-14 04:27:29 UTC
Created attachment 874233 [details]
File: open_fds

Comment 10 Joseph O Morrow 2014-03-14 04:27:30 UTC
Created attachment 874234 [details]
File: proc_pid_status

Comment 11 Joseph O Morrow 2014-03-14 04:27:32 UTC
Created attachment 874235 [details]
File: var_log_messages

Comment 12 Joseph O Morrow 2014-03-16 17:08:30 UTC
SIGSEGV seems to occur upon closing after apparent lua incompatibility soon after arriving at joringsbridge (first movement made after arrival diverts to what should be a conversation between several characters, but all action freezes except ability to press <esc> to exit). It is at this exit that SIGSEGV seems to occur.

I tried rebuilding strictly on lua 5.1 (using ccmake, adding /lua-5.1 to include path), after applying all but lua patch. Everything seems to work after that, but a segment-fault occurs upon every exit. I can try to grab the coredump to attach if needed (probably should be attached to a new/different bug report?)

Comment 13 Fedora End Of Life 2015-05-29 11:14:55 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. 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 EOL if it remains open with a Fedora  'version'
of '20'.

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.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 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 this bug is closed as described in the policy above.

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 14 Fedora End Of Life 2015-06-29 19:27:25 UTC
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

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