Bug 672688 - [abrt] ZipFile::getRawData was killed by signal 11 (SIGSEGV)
Summary: [abrt] ZipFile::getRawData was killed by signal 11 (SIGSEGV)
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: openoffice.org
Version: 14
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Caolan McNamara
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:04c7d0c401288f41bb7a48b3807...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-01-25 20:53 UTC by box963
Modified: 2011-02-16 16:27 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-02-16 16:27:41 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (42.27 KB, text/plain)
2011-01-25 20:53 UTC, box963 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description box963 2011-01-25 20:53:11 UTC 
abrt version: 1.1.14
architecture: i686
Attached file: backtrace
cmdline: /usr/lib/openoffice.org3/program/swriter.bin -writer
component: openoffice.org
crash_function: acquire
executable: /usr/lib/openoffice.org3/program/swriter.bin
kernel: 2.6.35.10-74.fc14.i686.PAE
package: openoffice.org-writer-1:3.3.0-19.2.fc14
rating: 4
reason: Process /usr/lib/openoffice.org3/program/swriter.bin was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1295984593
uid: 500

How to reproduce
-----
1. cut text from webpage
2.paste into oowriter
3.saved file -> crash
Comment 1 box963 2011-01-25 20:53:16 UTC 
Created attachment 475271 [details]
File: backtrace
Comment 2 Caolan McNamara 2011-01-25 21:08:08 UTC 
Are you able to reproduce this. We clearly don't crash on paste every time we paste from a web page.


(tech note: ZipFile::getRawData (this=0x0), we shouldn't have ended up in this situation, the intent is generally to throw on a failed m_pZipFile I think)
Comment 3 Caolan McNamara 2011-02-16 16:27:41 UTC 
Can't reproduce this, and can't see how the bt could have come about, shouldn't have been possible :-(
Note You need to log in before you can comment on or make changes to this bug.