Bug 708448 - [abrt] freeciv-2.2.5-1.fc14: overview_to_map_pos: Process /usr/bin/freeciv-gtk2 was killed by signal 6 (SIGABRT)
Summary: [abrt] freeciv-2.2.5-1.fc14: overview_to_map_pos: Process /usr/bin/freeciv-gt...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: freeciv
Version: 14
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Gwyn Ciesla
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:090d3febd9f2479395667246128...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-05-27 16:37 UTC by Henning Norén
Modified: 2012-02-02 14:43 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-02-02 14:43:54 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (16.60 KB, text/plain)
2011-05-27 16:37 UTC, Henning Norén 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Henning Norén 2011-05-27 16:37:21 UTC 
abrt version: 1.1.18
architecture: x86_64
Attached file: backtrace, 16995 bytes
cmdline: freeciv-gtk2
comment: The crash happened during a AI move of a lot of troops so I hid the window and then a while later opened it, hid it and opened it again in a quick sequence which then was followed by the crash
component: freeciv
Attached file: coredump, 294764544 bytes
crash_function: overview_to_map_pos
executable: /usr/bin/freeciv-gtk2
kernel: 2.6.35.13-91.fc14.x86_64
package: freeciv-2.2.5-1.fc14
rating: 4
reason: Process /usr/bin/freeciv-gtk2 was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
How to reproduce: 1. Not sure, happened during AI move when I hid and opened the freeciv window a few times
time: 1306514041
uid: 500
Comment 1 Henning Norén 2011-05-27 16:37:24 UTC 
Created attachment 501344 [details]
File: backtrace
Comment 2 Gwyn Ciesla 2012-02-02 14:43:54 UTC 
Fedora 14 is End-of-Life, please reopen against a current release if this bug is still occurring.  Thank you!
Note You need to log in before you can comment on or make changes to this bug.