Bug 739621

Summary: [abrt] openoffice.org-writer-1:3.2.0-12.35.fc13: cppu::throwException: (SIGBUS)
Product: [Fedora] Fedora Reporter: Peter Land <peland>
Component: openoffice.orgAssignee: Stephan Bergmann <sbergman>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 13CC: caolanm
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:0471f40b9db047aedd727d46eb04c01d1fdc1f6f
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-01-16 14:18:46 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace none

Description Peter Land 2011-09-19 16:11:53 UTC 
abrt version: 1.1.14
architecture: x86_64
Attached file: backtrace
cmdline: /usr/lib64/openoffice.org3/program/swriter.bin -writer
component: openoffice.org
crash_function: cppu::throwException
executable: /usr/lib64/openoffice.org3/program/swriter.bin
kernel: 2.6.34.9-69.fc13.x86_64
package: openoffice.org-writer-1:3.2.0-12.35.fc13
rating: 4
reason: Process /usr/lib64/openoffice.org3/program/swriter.bin was killed by signal 7 (SIGBUS)
release: Fedora release 13 (Goddard)
time: 1316447579
uid: 17045

How to reproduce
-----
1. Tried to save spreadsheet (open a very long time) as Microsoft XLS
2. OpenOffice died
3.
Comment 1 Peter Land 2011-09-19 16:11:56 UTC 
Created attachment 523864 [details]
File: backtrace
Comment 2 Caolan McNamara 2011-09-20 08:16:30 UTC 
SIGBUS, an unexpected signal to crash us.

a) Are you able to reproduce this
b) And/or is there anything interesting in /var/log/messages around the time it crashed.
Comment 3 Stephan Bergmann 2011-09-20 08:54:50 UTC 
If I'm not mistaken, the SIGBUS is merely due to a call instruction going nowhere.  Björn Michaelsen recently showed me a similar crash, but at that time I thought it was cppu::throwException successfully throwing an exception that was not caught anywhere up on the stack.  But with the SIGBUS, it looks rather like cppu::throwException is broken here (though still unclear why).