Bug 1179494

Summary: [abrt] lincity-ng: do_periodic_events(): lincity-ng killed by SIGFPE
Product: [Fedora] Fedora Reporter: Jacek Wielemborek <d33tah>
Component: lincity-ngAssignee: Tom "spot" Callaway <tcallawa>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 21CC: jimj_wpg, tcallawa
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/d29e30ffa210c435bdac52f7fe32971d97ac2c61
Whiteboard: abrt_hash:43b44b2ca8d6a44c5b6921e18021e9c59607d209
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-12-02 07:00:24 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: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Jacek Wielemborek 2015-01-06 22:21:14 UTC
Description of problem:
This happened after choosing a map in the "new game" menu.

Version-Release number of selected component:
lincity-ng-2.9-0.4.beta.fc21

Additional info:
reporter:       libreport-2.3.0
backtrace_rating: 4
cmdline:        lincity-ng
crash_function: do_periodic_events
executable:     /usr/bin/lincity-ng
kernel:         3.17.7-300.fc21.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (5 frames)
 #0 do_periodic_events at src/lincity/simulate.cpp:136
 #1 do_time_step at src/lincity/simulate.cpp:120
 #2 execute_timestep at src/lincity-ng/MainLincity.cpp:75
 #3 Game::run at src/lincity-ng/Game.cpp:292
 #4 mainLoop at src/lincity-ng/main.cpp:423

Comment 1 Jacek Wielemborek 2015-01-06 22:21:18 UTC
Created attachment 976966 [details]
File: backtrace

Comment 2 Jacek Wielemborek 2015-01-06 22:21:19 UTC
Created attachment 976967 [details]
File: cgroup

Comment 3 Jacek Wielemborek 2015-01-06 22:21:20 UTC
Created attachment 976968 [details]
File: core_backtrace

Comment 4 Jacek Wielemborek 2015-01-06 22:21:22 UTC
Created attachment 976969 [details]
File: dso_list

Comment 5 Jacek Wielemborek 2015-01-06 22:21:23 UTC
Created attachment 976970 [details]
File: environ

Comment 6 Jacek Wielemborek 2015-01-06 22:21:24 UTC
Created attachment 976971 [details]
File: limits

Comment 7 Jacek Wielemborek 2015-01-06 22:21:26 UTC
Created attachment 976972 [details]
File: maps

Comment 8 Jacek Wielemborek 2015-01-06 22:21:27 UTC
Created attachment 976973 [details]
File: open_fds

Comment 9 Jacek Wielemborek 2015-01-06 22:21:28 UTC
Created attachment 976974 [details]
File: proc_pid_status

Comment 10 Jacek Wielemborek 2015-01-06 22:21:29 UTC
Created attachment 976975 [details]
File: var_log_messages

Comment 11 Fedora End Of Life 2015-11-04 11:20:29 UTC
This message is a reminder that Fedora 21 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 21. 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 '21'.

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 21 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 12 Fedora End Of Life 2015-12-02 07:00:26 UTC
Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 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.