Bug 652855

Summary:

[abrt] ultimatestunts-0.7.5-5.fc12: CBinBuffer::getUint8: Process /usr/bin/ustunts was killed by signal 11 (SIGSEGV)

Product:

[Fedora] Fedora

Reporter:

C.J.H. <cogre666>

Component:

ultimatestunts

Assignee:

Dan Horák <dan>

Status:

CLOSED ERRATA

QA Contact:

Fedora Extras Quality Assurance <extras-qa>

Severity:

medium

Docs Contact:

Priority:

low

Version:

CC:

alizekft, dan

Target Milestone:

---

Target Release:

---

Hardware:

x86_64

OS:

Unspecified

Whiteboard:

abrt_hash:48494f627689b38960099e511ce5210a48e7c43f

Fixed In Version:

ultimatestunts-0.7.5-6.fc13

Doc Type:

Bug Fix

Doc Text:

Story Points:

---

Clone Of:

Environment:

Last Closed:

2011-04-21 05:29:48 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

Description C.J.H. 2010-11-13 00:10:02 UTC

abrt version: 1.1.13
architecture: x86_64
Attached file: backtrace
cmdline: /usr/bin/ustunts
comment: Completed the default track, watched the replay, at end of replay the game crashed. I expected to be taken back to the replay menu, or at least the new game menu.
component: ultimatestunts
crash_function: CBinBuffer::getUint8
executable: /usr/bin/ustunts
kernel: 2.6.35.6-48.fc14.x86_64
package: ultimatestunts-0.7.5-5.fc12
rating: 4
reason: Process /usr/bin/ustunts was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1289606456
uid: 1000

How to reproduce
-----
1.ran ultimate stunts,
2.selected a 1 player race
3.changed player name
4.changed colour of the car to a dark blue, & changed type of car to Formula 1
5.raced the default track
6.completed the track
7.selected to view a replay
8.watched the replay and at the end of the replay the game crashed

Comment 1 C.J.H. 2010-11-13 00:10:04 UTC

Created attachment 460174 [details]
File: backtrace

Comment 2 Dan Horák 2011-04-16 12:54:35 UTC

*** Bug 697052 has been marked as a duplicate of this bug. ***

Comment 3 Fedora Update System 2011-04-16 15:34:21 UTC

ultimatestunts-0.7.5-6.fc14 has been submitted as an update for Fedora 14.
https://admin.fedoraproject.org/updates/ultimatestunts-0.7.5-6.fc14

Comment 4 Fedora Update System 2011-04-16 15:34:29 UTC

ultimatestunts-0.7.5-6.fc13 has been submitted as an update for Fedora 13.
https://admin.fedoraproject.org/updates/ultimatestunts-0.7.5-6.fc13

Comment 5 Fedora Update System 2011-04-16 15:34:38 UTC

ultimatestunts-0.7.5-7.fc15 has been submitted as an update for Fedora 15.
https://admin.fedoraproject.org/updates/ultimatestunts-0.7.5-7.fc15

Comment 6 Fedora Update System 2011-04-16 20:59:00 UTC

Package ultimatestunts-0.7.5-6.fc14:
* should fix your issue,
* was pushed to the Fedora 14 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing ultimatestunts-0.7.5-6.fc14'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/ultimatestunts-0.7.5-6.fc14
then log in and leave karma (feedback).

Comment 7 Fedora Update System 2011-04-21 05:29:44 UTC

ultimatestunts-0.7.5-7.fc15 has been pushed to the Fedora 15 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 8 Fedora Update System 2011-04-30 23:20:59 UTC

ultimatestunts-0.7.5-6.fc14 has been pushed to the Fedora 14 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 9 Fedora Update System 2011-04-30 23:21:55 UTC

ultimatestunts-0.7.5-6.fc13 has been pushed to the Fedora 13 stable repository.  If problems still persist, please make note of it in this bug report.