Bug 653061 - [abrt] openoffice.org-writer-1:3.2.0-12.33.fc13: Process /usr/lib64/openoffice.org3/program/swriter.bin was killed by signal 11 (SIGSEGV)
Summary: [abrt] openoffice.org-writer-1:3.2.0-12.33.fc13: Process /usr/lib64/openoffic...
Alias: None
Product: Fedora
Classification: Fedora
Component: openoffice.org
Version: 13
Hardware: x86_64
OS: Unspecified
Target Milestone: ---
Assignee: Caolan McNamara
QA Contact: Fedora Extras Quality Assurance
Whiteboard: abrt_hash:89098ffed879ed0da7dd170043a...
Depends On:
TreeView+ depends on / blocked
Reported: 2010-11-14 10:14 UTC by alexander
Modified: 2010-11-24 14:39 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2010-11-24 14:39:53 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (615 bytes, text/plain)
2010-11-14 10:14 UTC, alexander
no flags Details

Description alexander 2010-11-14 10:14:31 UTC
abrt version: 1.1.13
architecture: x86_64
cmdline: /usr/lib64/openoffice.org3/program/swriter.bin -writer file:///home/axel/Documents/English/Translare%20A%20Practical%20Guide%20to%20Fedora%20and%20Red%20Hat%20%20.odt
component: openoffice.org
executable: /usr/lib64/openoffice.org3/program/swriter.bin
package: openoffice.org-writer-1:3.2.0-12.33.fc13
rating: 4
reason: Process /usr/lib64/openoffice.org3/program/swriter.bin was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)
time: 1289670060
uid: 500

[New Thread 19782]
[New Thread 19783]
[New Thread 19784]
[New Thread 19787]
[New Thread 19803]
[New Thread 19785]
[New Thread 19786]
warning: "/var/cache/abrt-di/usr/lib/debug/.build-id/98/3a8bf14c249d18b3c6f32635c0f1fcadc1d440.debug": separate debug info file has no debug info
Core was generated by `/usr/lib64/openoffice.org3/program/swriter.bin -writer file:///home/axel/Docume'.
Program terminated with signal 11, Segmentation fault.
#0  SwClientIter::SwClientIter (this=0x7fff371400e0, rModify=...)
    at /usr/src/debug/OOO320_m12/sw/source/core/attr/calbck.cxx:481

Timeout exceeded: 60 second, killing gdb

Comment 1 alexander 2010-11-14 10:14:33 UTC
Created attachment 460350 [details]
File: backtrace

Comment 2 David Tardon 2010-11-14 13:23:49 UTC
The stack trace is cut off, unfortunately. Is there a way to reproduce the crash?

Comment 3 David Tardon 2010-11-24 14:39:53 UTC
Feel free to reopen if you know how it happened.

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