wvWare crashed with SIGSEGV in *__GI_strcpy()

[Laurent Bonnaud]

Binary package hint: wv

This crash occurred while tracker was indexing my homedir. Unfortunately tracker does not tell which file triggers this bug (only the copy in /tmp is known but insufficient).

ProblemType: Crash
Architecture: i386
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/wvWare
Package: wv 1.2.4-2ubuntu2 [modified: usr/bin/wvWare usr/bin/wvRTF usr/bin/wvConvert usr/bin/wvVersion usr/bin/wvSummary]
ProcCmdline: /usr/bin/wvWare -1 -x /usr/share/wv/wvHtml.xml -d /tmp -b wv-uVvzOd /tmp/tracker.msword_filter.zGOKmJqGzJ/tmpfile
ProcCwd: /tmp/tracker.msword_filter.zGOKmJqGzJ
ProcEnviron:
 LC_PAPER=fr_FR.UTF-8
 SHELL=/bin/bash
 PATH=(custom, user)
 LC_COLLATE=C
 LANG=en_US.UTF-8
Signal: 11
SourcePackage: wv
StacktraceTop:
 *__GI_strcpy (dest=<value optimized out>, src=<value optimized out>) at strcpy.c:39
 ?? () from /usr/lib/libwv-1.2.so.3
 xmlParseStartTag () from /usr/lib/libxml2.so.2
 xmlParseElement () from /usr/lib/libxml2.so.2
 xmlParseContent () from /usr/lib/libxml2.so.2
Title: wvWare crashed with SIGSEGV in *__GI_strcpy()
Uname: Linux 2.6.28-11-generic i686
UserGroups: adm admin audio cdrom dialout dip floppy fuse kvm lpadmin plugdev pulse pulse-access pulse-rt scanner staff video

[Laurent Bonnaud (laurent-bonnaud)]

Some /tmp/tracker.msword_filter.* directories remain in /tmp after tracker has indexed them. Unfortunately the directory containing the file causing the crash is not there any longer.

[Apport retracing service (apport)]

StacktraceTop:*__GI_strcpy (dest=0xbfe3c070 "\v", src=0x0) at strcpy.c:39
exstartElement (userData=0xbfe3f1d0,
xmlParseStartTag () from /usr/lib/libxml2.so.2
xmlParseElement () from /usr/lib/libxml2.so.2
xmlParseContent () from /usr/lib/libxml2.so.2

[Laurent Bonnaud (laurent-bonnaud)]

I tagged this bug as a security problem because it can be triggered by just receiving an email with a MS-Word file.

[Jamie Strandboge (jdstrand)]

Thank you for using Ubuntu and taking the time to report a bug. If you could determine the file causing the problem, it would help in fixing this issue.

[Vish (vish)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future.
To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New".