baloo_file_extractor crashed with SIGSEGV in Xapian::Database::get_document()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
baloo (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
baloo_file_
ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: baloo 4:4.12.97-0ubuntu1
ProcVersionSign
Uname: Linux 3.13.0-23-generic x86_64
ApportVersion: 2.14.1-0ubuntu1
Architecture: amd64
CrashCounter: 1
CurrentDesktop: KDE
Date: Sat Apr 5 12:24:51 2014
ExecutablePath: /usr/bin/
InstallationDate: Installed on 2013-11-24 (131 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
ProcCmdline: /usr/bin/
SegvAnalysis:
Segfault happened at: 0x7f46abb16e78 <_ZNK6Xapian8Da
PC (0x7f46abb16e78) ok
source "0x10(%rsi)" (0x00000010) not located in a known VMA region (needed readable region)!
destination "%rcx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: baloo
Stacktrace:
#0 0x00007f46abb16e78 in Xapian:
No symbol table info available.
#1 0x0000000000408f2e in _start ()
No symbol table info available.
StacktraceTop:
Xapian:
_start ()
Title: baloo_file_
UpgradeStatus: Upgraded to trusty on 2014-01-13 (81 days ago)
UserGroups: adm cdrom debian-tor dip lpadmin plugdev sambashare sudo
Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1301742, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.