tracker crashed with SIGSEGV in strstr()

Bug #149002 reported by Jukka Kosonen
10
Affects Status Importance Assigned to Milestone
tracker (Ubuntu)
New
Medium
Unassigned

Bug Description

Binary package hint: tracker

I wasn't using trackr,, it was just indexing my files. There is about 11GB new files in my home folder copied from a backup about 2 hours ago.

ProblemType: Crash
Architecture: i386
Date: Thu Oct 4 18:19:02 2007
DistroRelease: Ubuntu 7.10
ExecutablePath: /usr/bin/trackerd
NonfreeKernelModules: cdrom
Package: tracker 0.6.3-0ubuntu2
PackageArchitecture: i386
ProcCmdline: trackerd
ProcCwd: /home/jtk
ProcEnviron:
 PATH=/home/jtk/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: tracker
Stacktrace:
 #0 0xb7bd2f37 in strstr () from /lib/tls/i686/cmov/libc.so.6
 #1 0x080568a5 in ?? ()
 #2 0x00000000 in ?? ()
StacktraceTop:
 strstr () from /lib/tls/i686/cmov/libc.so.6
 ?? ()
 ?? ()
Title: trackerd crashed with SIGSEGV in strstr()
Uname: Linux P7120 2.6.22-12-generic #1 SMP Sun Sep 23 18:11:30 GMT 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video

Tags: apport-crash
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:strstr () from /lib/tls/i686/cmov/libc.so.6
tracker_indexer_merge_indexes (type=INDEX_TYPE_FILES) at tracker-indexer.c:194
process_files_thread () at trackerd.c:1158
g_thread_create_proxy (data=0x80f2970) at /build/buildd/glib2.0-2.14.1/glib/gthread.c:635
start_thread () from /lib/tls/i686/cmov/libpthread.so.0

Revision history for this message
Apport retracing service (apport) wrote : Stack trace with source code
Changed in tracker:
importance: Undecided → Medium
Revision history for this message
Attila Darázs (darazs) wrote :

I also experience this bug after copying about 25 GB of new files from an NTFS partition.

I think that some of my files have weird files names (after some wrong UTF8 <-> ISO 8859-2 encoding). So maybe the filename parsing algorithm is what does the crashing.
It always crashes like this after some minutes after I start my computer and log in.

This is only a guess, but maybe a good starting point for the bughunter!

Revision history for this message
jyk (jykaminski) wrote :

same crash with amd64 architecture

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.