GNOME Bugzilla – Bug 403887
[apport] tracker-extract crashed with SIGSEGV in strlen()
Last modified: 2007-07-09 19:20:36 UTC
Steps to reproduce: 1. Index a ico file in tracker 0.5.4 in Ubuntu Feisty Fawn 2. 3. Stack trace: Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". Core was generated by `tracker-extract /media/hda5/cs/freevo2/share/freevo/htdocs/favicon.ico image/x-'. Program terminated with signal 11, Segmentation fault.
+ Trace 107626
Other information: From https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/82879
Please build the package with debugging symbols, and provide a stack trace.
I build the package with debugging symbols, but now tracker-extract does not crash or give any output to standard out. file on the offending file gives: file /media/hda5/cs/freevo2/share/freevo/htdocs/favicon.ico /media/hda5/cs/freevo2/share/freevo/htdocs/favicon.ico: PNG image data, CORRUPTED, running tracker-extract on that: nothing on standard out
I seem to have the same problem. I added debug symbols by means of apport-retrace. The stack trace and core dump can be found here: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/84000 Let me know if you need something else.
Created attachment 82158 [details] File causing the crash
I've had the same type of crash with the same error (strlen). However, it happened when I was unpacking a tar.gz file. Afterwards it had no problem indexing the generated directory, it was only that _during_ the unpacking it crashed. The fact that you cannot reproduce the crash suggests its not the contents of the file that was causing the crash, but the fact it was modified at the very moment it got indexed. Since there are on launchpad several pretty identical crash-reports about different filetypes suggests its not a file-specific or even data-specific problem. Just my two cents. I may be completely off with my wild guess work here, so i'll hold off on marking them all duplicates of this one ;-)
Im closing this provisionally - if it still persists with latest svn then let me know or repopen this bug as I cant replicate it