Bug 592259 - [abrt] crash in abiword-1:2.8.4-1.fc12: raise: Process /usr/bin/abiword was killed by signal 6 (SIGABRT)
[abrt] crash in abiword-1:2.8.4-1.fc12: raise: Process /usr/bin/abiword was k...
Status: CLOSED UPSTREAM
Product: Fedora
Classification: Fedora
Component: abiword (Show other bugs)
12
i686 Linux
low Severity medium
: ---
: ---
Assigned To: Marc Maurer
Fedora Extras Quality Assurance
abrt_hash:4027b768068781c0e7af2be666c...
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2010-05-14 07:36 EDT by Chris Campbell
Modified: 2010-11-07 09:40 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-06-29 07:57:26 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
File: backtrace (19.16 KB, text/plain)
2010-05-14 07:36 EDT, Chris Campbell
no flags Details

  None (edit)
Description Chris Campbell 2010-05-14 07:36:31 EDT
abrt 1.0.9 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: abiword
comment: I don't remember
component: abiword
crash_function: raise
executable: /usr/bin/abiword
global_uuid: 4027b768068781c0e7af2be666c329d1f9cd725c
kernel: 2.6.32.11-99.fc12.i686
package: abiword-1:2.8.4-1.fc12
rating: 4
reason: Process /usr/bin/abiword was killed by signal 6 (SIGABRT)
release: Fedora release 12 (Constantine)

How to reproduce
-----
1. I don't remember
2.
3.
Comment 1 Chris Campbell 2010-05-14 07:36:33 EDT
Created attachment 414021 [details]
File: backtrace
Comment 2 Chris Campbell 2010-06-29 07:57:26 EDT

-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers
Comment 3 hwQQUo 2010-11-06 11:47:15 EDT
I committed a Band-Aid fix for the crash upstream: http://www.abisource.com/viewvc?view=rev&revision=29400
Comment 4 Marc Maurer 2010-11-07 09:40:01 EST
Marking closed upstream as per comment 3

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