Bug 1017610

Summary: [abrt] warzone2100-3.1.0-1.fc18: drawRadarBlips: Process /usr/bin/warzone2100 was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Dimitar H Dimitrov <dimityr_7>
Component: warzone2100Assignee: Karol Trzcionka <karlikt>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 18CC: jsynacek, karlikt
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:11a02cdffd72ed54d94d633d66bec2bd516601a3
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-02-05 22:27:33 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

Description Dimitar H Dimitrov 2013-10-10 08:50:28 UTC 
Description of problem:
1. Start WareZone game
2. Load saved scrimish game
3. Game was crashed 
4. Back to desktop, the resolution was not restored 

Version-Release number of selected component:
warzone2100-3.1.0-1.fc18

Additional info:
reporter:       libreport-2.1.7
backtrace_rating: 4
cmdline:        /usr/bin/warzone2100
crash_function: drawRadarBlips
executable:     /usr/bin/warzone2100
kernel:         3.10.14-100.fc18.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000
var_log_messages: Oct 10 11:46:38 localhost abrt[5158]: Saved core dump of pid 5085 (/usr/bin/warzone2100) to /var/tmp/abrt/ccpp-2013-10-10-11:46:31-5085 (2292256768 bytes)

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 drawRadarBlips at intdisplay.cpp:3190
 #1 drawRadar at radar.cpp:310
 #2 draw3DScene at display3d.cpp:751
 #3 displayWorld at display.cpp:1247
 #4 renderLoop at loop.cpp:324
 #5 gameLoop at loop.cpp:696
 #6 runGameLoop at main.cpp:892
 #7 mainLoop at main.cpp:998
 #8 wzMain3 at main_sdl.cpp:1257
 #9 realmain at main.cpp:1332
Comment 1 Dimitar H Dimitrov 2013-10-10 08:50:33 UTC 
Created attachment 810380 [details]
File: backtrace
Comment 2 Dimitar H Dimitrov 2013-10-10 08:50:36 UTC 
Created attachment 810381 [details]
File: cgroup
Comment 3 Dimitar H Dimitrov 2013-10-10 08:50:39 UTC 
Created attachment 810382 [details]
File: core_backtrace
Comment 4 Dimitar H Dimitrov 2013-10-10 08:50:43 UTC 
Created attachment 810383 [details]
File: dso_list
Comment 5 Dimitar H Dimitrov 2013-10-10 08:50:46 UTC 
Created attachment 810384 [details]
File: environ
Comment 6 Dimitar H Dimitrov 2013-10-10 08:50:51 UTC 
Created attachment 810385 [details]
File: exploitable
Comment 7 Dimitar H Dimitrov 2013-10-10 08:50:55 UTC 
Created attachment 810386 [details]
File: limits
Comment 8 Dimitar H Dimitrov 2013-10-10 08:50:59 UTC 
Created attachment 810387 [details]
File: maps
Comment 9 Dimitar H Dimitrov 2013-10-10 08:51:02 UTC 
Created attachment 810388 [details]
File: open_fds
Comment 10 Dimitar H Dimitrov 2013-10-10 08:51:05 UTC 
Created attachment 810389 [details]
File: proc_pid_status
Comment 11 Fedora End Of Life 2013-12-21 14:39:30 UTC 
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.
Comment 12 Fedora End Of Life 2014-02-05 22:27:33 UTC 
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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.