Bug 587426 - [abrt] crash in ballz-1.0.1-3.fc12: Process /usr/bin/ballz was killed by signal 6 (SIGABRT)
Summary: [abrt] crash in ballz-1.0.1-3.fc12: Process /usr/bin/ballz was killed by sign...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: ballz
Version: 12
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Hans de Goede
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:5abe67865f123ef9a118456419f...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-04-29 21:08 UTC by armando.fella
Modified: 2010-06-22 10:31 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-06-22 10:31:09 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (17.60 KB, text/plain)
2010-04-29 21:08 UTC, armando.fella 		no flags Details
View All

Description armando.fella 2010-04-29 21:08:30 UTC 
abrt 1.0.9 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: /usr/bin/ballz
component: ballz
executable: /usr/bin/ballz
global_uuid: 5abe67865f123ef9a118456419fae506ae5c4d09
kernel: 2.6.32.11-99.fc12.x86_64
package: ballz-1.0.1-3.fc12
rating: 4
reason: Process /usr/bin/ballz was killed by signal 6 (SIGABRT)
release: Fedora release 12 (Constantine)
Comment 1 armando.fella 2010-04-29 21:08:32 UTC 
Created attachment 410233 [details]
File: backtrace
Comment 2 Hans de Goede 2010-06-22 10:31:09 UTC 
Hi,

Thanks for the bug report.

Looking at the backtrace you send a sigterm (signal 15) to ballz in some way (maybe you closed the terminal from which you started it, or you were logging out?), which got intercepted by allegro (the gaming library ballz) uses and then turned into an abort which got intercepted by abrt.

Doing an abort is allegro's standard behaviour when an allegro using game is not exited cleanly, so I don't consider this a bug.

Regards,

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