Bug 628425

Summary: [abrt] openoffice.org-writer-1:3.2.0-12.31.fc13: GetNode: Process /usr/lib/openoffice.org3/program/swriter.bin was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Sebastián Ramírez <teo78>
Component: openoffice.orgAssignee: Caolan McNamara <caolanm>
Status: CLOSED UPSTREAM QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 13CC: caolanm
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard: abrt_hash:0ae226f4832b83f7c6c18195168818d7071b5d57
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-08-30 08:48:43 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 Sebastián Ramírez 2010-08-30 02:53:22 UTC
abrt version: 1.1.13
architecture: i686
Attached file: backtrace
cmdline: /usr/lib/openoffice.org3/program/swriter.bin -writer
component: openoffice.org
crash_function: GetNode
executable: /usr/lib/openoffice.org3/program/swriter.bin
kernel: 2.6.33.8-149.fc13.i686
package: openoffice.org-writer-1:3.2.0-12.31.fc13
rating: 4
reason: Process /usr/lib/openoffice.org3/program/swriter.bin was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)
time: 1283119399
uid: 500

Comment 1 Sebastián Ramírez 2010-08-30 02:54:00 UTC
Created an attachment (id=441870)
File: backtrace

Comment 2 Caolan McNamara 2010-08-30 08:43:32 UTC
Do you know how to reproduce this ?

Comment 3 Caolan McNamara 2010-08-30 08:48:43 UTC
filed a patch upstream to avoid this crash, but still want to know how it happened in order to make a complete fix