Bug 682472 - [abrt] gl-117-1.3.2-10.fc15: do_lookup_x: Process /usr/bin/gl-117 was killed by signal 11 (SIGSEGV)
Summary: [abrt] gl-117-1.3.2-10.fc15: do_lookup_x: Process /usr/bin/gl-117 was killed ...
Keywords:
Status: CLOSED DUPLICATE of bug 682307
Alias: None
Product: Fedora
Classification: Fedora
Component: gl-117
Version: 15
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Steven Pritchard
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:29ad1ad8c7b5c07d2275ef8dd72...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-05 20:42 UTC by John Watzke
Modified: 2011-03-06 17:02 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-03-06 17:02:40 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (27.60 KB, text/plain)
2011-03-05 20:42 UTC, John Watzke
no flags Details

Description John Watzke 2011-03-05 20:42:23 UTC
abrt version: 1.1.17
architecture: i686
Attached file: backtrace, 28261 bytes
cmdline: gl-117
comment: Always seems to crash when I start this game
component: gl-117
Attached file: coredump, 1323008 bytes
crash_function: do_lookup_x
executable: /usr/bin/gl-117
kernel: 2.6.38-0.rc6.git6.1.fc15.i686.PAE
package: gl-117-1.3.2-10.fc15
rating: 4
reason: Process /usr/bin/gl-117 was killed by signal 11 (SIGSEGV)
release: Fedora release 15 (Lovelock)
How to reproduce: 1. Start GL-117
time: 1299357638
uid: 500

Comment 1 John Watzke 2011-03-05 20:42:25 UTC
Created attachment 482471 [details]
File: backtrace

Comment 2 John Watzke 2011-03-05 20:44:56 UTC
The backtrace looks very similar to a crash I got when starting another game, Warzone 2100.  That bug was filed as bug 682398 and it seems that game may be suffering from the same issue as this game.

Comment 3 John Watzke 2011-03-06 17:02:40 UTC
This is actually caused by the do_lookup_x regression in glibc.  Downgrading glibc to the -3 version makes this game work again.

*** This bug has been marked as a duplicate of bug 682307 ***


Note You need to log in before you can comment on or make changes to this bug.