[apport] trackerd crashed with SIGSEGV

Bug #89834 reported by Leon van der Ree
0
Affects Status Importance Assigned to Milestone
tracker (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

Binary package hint: tracker

no idea when this happend

ProblemType: Crash
Architecture: i386
Date: Mon Mar 5 10:50:16 2007
DistroRelease: Ubuntu 7.04
ExecutablePath: /usr/bin/trackerd
Package: tracker 0.5.4-1ubuntu1
ProcCmdline: trackerd
ProcCwd: /home/leon
ProcEnviron:
 LANGUAGE=nl_NL.UTF-8@euro
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games
 LANG=nl_NL.UTF-8@euro
 SHELL=/bin/bash
Signal: 11
SourcePackage: tracker
Stacktrace:
 #0 0x08078626 in ?? ()
 #1 0x080ad8e8 in ?? ()
 #2 0x081ba150 in ?? ()
 #3 0xb72241a8 in ?? ()
 #4 0x00000000 in ?? ()
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Uname: Linux leon-laptop 2.6.20-9-generic #2 SMP Mon Feb 26 03:01:44 UTC 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev scanner video

Revision history for this message
Leon van der Ree (lvanderree) wrote :
Revision history for this message
Emilio Pozuelo Monfort (pochu) wrote :

Backtrace with debug symbols

Changed in tracker:
importance: Undecided → Medium
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:tracker_db_index_file (db_con=0x81633d0, info=0xb695aad8, is_attachment=0) at tracker-db.c:955
tracker_db_index_entity (db_con=0x81633d0, info=0xb695aad8) at tracker-db.c:1084
process_files_thread () at trackerd.c:1353
IA__g_thread_create_full (func=0x8158d58, data=0xb7224480, stack_size=3072476288, joinable=-1222491008, bound=-1222491008, priority=G_THREAD_PRIORITY_LOW,

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Emilio Pozuelo Monfort (pochu) wrote :

Thanks for your report

Changed in tracker:
status: Unconfirmed → Confirmed
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.