Ubuntu

tracker-indexer crashed with SIGSEGV in tracker_db_interface_execute_vquery()

Reported by Chrescht on 2010-08-17
22
This bug affects 3 people
Affects Status Importance Assigned to Milestone
tracker (Ubuntu)
Medium
Unassigned

Bug Description

Binary package hint: tracker

The tracker was indexing when this happened..
This is not the first crash.
I installed the tracker only recently so the index is not yet entirely built.

There might be a file that it doesn't like to index..but I don't know which one.

cheers.

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: tracker 0.6.95-1ubuntu6
ProcVersionSignature: Ubuntu 2.6.32-24.39-generic 2.6.32.15+drm33.5
Uname: Linux 2.6.32-24-generic i686
Architecture: i386
CrashCounter: 1
Date: Tue Aug 17 01:09:48 2010
ExecutablePath: /usr/lib/tracker/tracker-indexer
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
ProcCmdline: /usr/lib/tracker/tracker-indexer
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.utf8
SegvAnalysis:
 Segfault happened at: 0x6128f9: cmpb $0x0,(%eax)
 PC (0x006128f9) ok
 source "$0x0" ok
 destination "(%eax)" (0x00000000) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: tracker
StacktraceTop:
 ?? () from /usr/lib/libsqlite3.so.0
 ?? () from /usr/lib/libsqlite3.so.0
 ?? () from /usr/lib/libsqlite3.so.0
 ?? () from /usr/lib/tracker/libtracker-db.so.0
 tracker_db_interface_execute_vquery ()
Title: tracker-indexer crashed with SIGSEGV in tracker_db_interface_execute_vquery()
UserGroups: vboxusers

Chrescht (sekateur) wrote :

StacktraceTop:
 sqlite3RunParser (pParse=0xa27f9a0,
 sqlite3Prepare (db=0x99b1da0, zSql=<value optimized out>,
 sqlite3LockAndPrepare (db=0x99b1da0, zSql=0x0, nBytes=-1,
 ?? () from /usr/lib/tracker/libtracker-db.so.0
 tracker_db_interface_execute_vquery ()

Changed in tracker (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Chrescht (sekateur) on 2010-09-25
visibility: private → public
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in tracker (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers