Bug 661754 - [abrt] antiword-0.37-9.fc12: vName2String: Process /usr/bin/antiword.bin was killed by signal 11 (SIGSEGV)
Summary: [abrt] antiword-0.37-9.fc12: vName2String: Process /usr/bin/antiword.bin was ...
Keywords:
Status: CLOSED CANTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: antiword
Version: 12
Hardware: i686
OS: Unspecified
low
medium
Target Milestone: ---
Assignee: Adrian Reber
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:b148829c2a69986c2b3909b9d31...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-12-09 15:40 UTC by Leonard J. Umina
Modified: 2012-03-26 08:22 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-03-26 08:22:02 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (82.15 KB, text/plain)
2010-12-09 15:40 UTC, Leonard J. Umina 		no flags Details
View All

Description Leonard J. Umina 2010-12-09 15:40:56 UTC 
abrt version: 1.1.13
architecture: i686
Attached file: backtrace
cmdline: antiword.bin -t -i 1 -m UTF-8 /tmp/rcltmpfVDqrC5.doc
component: antiword
crash_function: vName2String
executable: /usr/bin/antiword.bin
kernel: 2.6.32.26-175.fc12.i686.PAE
package: antiword-0.37-9.fc12
rating: 4
reason: Process /usr/bin/antiword.bin was killed by signal 11 (SIGSEGV)
release: Fedora release 12 (Constantine)
time: 1291908913
uid: 500

How to reproduce
-----
1. I was reindexing my disk with recoll
2.
3.
Comment 1 Leonard J. Umina 2010-12-09 15:40:59 UTC 
Created attachment 467770 [details]
File: backtrace
Comment 2 Leonard J. Umina 2010-12-09 16:08:54 UTC 
Package: antiword-0.37-9.fc12
Architecture: i686
OS Release: Fedora release 12 (Constantine)


How to reproduce
-----
1. I was reindexing my disk with recoll
2.
3.
Comment 3 Adrian Reber 2010-12-09 16:21:26 UTC 
Can you provide the document with which antiword crashes?
Comment 4 Adrian Reber 2012-03-26 08:22:02 UTC 
Closing it CANTFIX. Please reopen if you can provide the document which crashes antiword.
Note You need to log in before you can comment on or make changes to this bug.