abrt version: 1.1.13 architecture: i686 Attached file: backtrace cmdline: /usr/lib/openoffice.org3/program/soffice.bin -base component: openoffice.org crash_function: com::sun::star::uno::Sequence<signed char>::Sequence executable: /usr/lib/openoffice.org3/program/soffice.bin kernel: 2.6.35.6-48.fc14.i686 package: openoffice.org-brand-1:3.3.0-14.1.fc14 rating: 3 reason: Process /usr/lib/openoffice.org3/program/soffice.bin was killed by signal 6 (SIGABRT) release: Fedora release 14 (Laughlin) time: 1290498341 uid: 500 How to reproduce ----- 1. seek or sort in database form 2. 3.
Created attachment 462259 [details] File: backtrace
The len arg. in com::sun::star::uno::Sequence<signed char>::Sequence (this=0x8a7de790, len=-26401) is obviously nonsense and other values read from the db file in ZipFile::readLOC look suspicious too. The file is probably corrupted.
Yeah, I can reproduce this if I hard code that number in there. We should probably catch the bad_alloc and throw a ZipException to indicate a broken zip file
avoid crash in >= 3.3.0-16.5
openoffice.org-3.3.0-17.2.fc14 has been submitted as an update for Fedora 14. https://admin.fedoraproject.org/updates/openoffice.org-3.3.0-17.2.fc14
openoffice.org-3.3.0-17.2.fc14 has been pushed to the Fedora 14 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update openoffice.org'. You can provide feedback for this update here: https://admin.fedoraproject.org/updates/openoffice.org-3.3.0-17.2.fc14
openoffice.org-3.3.0-17.2.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report.