baloo_file_extractor crashed with SIGSEGV in memcpy()

Bug #1304206 reported by valerio
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
baloo (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

I was playing around with my music collection to solve bug #1299364.

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: baloo 4:4.12.97-0ubuntu2
Uname: Linux 3.14.0 x86_64
ApportVersion: 2.14.1-0ubuntu1
Architecture: amd64
CurrentDesktop: KDE
Date: Tue Apr 8 08:30:05 2014
ExecutablePath: /usr/bin/baloo_file_extractor
InstallationDate: Installed on 2014-02-13 (53 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
ProcCmdline: /usr/bin/baloo_file_extractor --bdata /media/username/Media/Quarantena/tmp4/Antony\ And\ The\ Johnsons/The\ Crying\ Light/01\ Her\ Eyes\ Are\ Underneath\ The\ Ground.flac
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
 LANGUAGE=
SegvAnalysis:
 Segfault happened at: 0x7fcd73d04e3e <__memcpy_sse2_unaligned+46>: movdqu -0x10(%rsi,%rdx,1),%xmm8
 PC (0x7fcd73d04e3e) ok
 source "-0x10(%rsi,%rdx,1)" (0x10259ffef) not located in a known VMA region (needed readable region)!
 destination "%xmm8" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: baloo
StacktraceTop:
 TagLib::ByteVector::replace(TagLib::ByteVector const&, TagLib::ByteVector const&) () from /usr/lib/x86_64-linux-gnu/libtag.so.1
 TagLib::ID3v2::SynchData::decode(TagLib::ByteVector const&) () from /usr/lib/x86_64-linux-gnu/libtag.so.1
 TagLib::ID3v2::FrameFactory::createFrame(TagLib::ByteVector const&, TagLib::ID3v2::Header*) const () from /usr/lib/x86_64-linux-gnu/libtag.so.1
 TagLib::ID3v2::Tag::parse(TagLib::ByteVector const&) () from /usr/lib/x86_64-linux-gnu/libtag.so.1
 TagLib::ID3v2::Tag::read() () from /usr/lib/x86_64-linux-gnu/libtag.so.1
Title: baloo_file_extractor crashed with SIGSEGV in TagLib::ByteVector::replace()
UpgradeStatus: Upgraded to trusty on 2014-02-14 (52 days ago)
UserGroups: adm bluetooth cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
valerio (passini-valerio) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 memcpy (__len=<optimized out>, __src=0x25a0000, __dest=0x256668e) at /usr/include/x86_64-linux-gnu/bits/string3.h:51
 TagLib::ByteVector::replace (this=0x7fff74927680, pattern=..., with=...) at ../../taglib/toolkit/tbytevector.cpp:551
 TagLib::ID3v2::SynchData::decode (data=...) at ../../taglib/mpeg/id3v2/id3v2synchdata.cpp:83
 TagLib::ID3v2::FrameFactory::createFrame (this=0x7fcd6186fcb0 <TagLib::ID3v2::FrameFactory::factory>, origData=..., tagHeader=<optimized out>) at ../../taglib/mpeg/id3v2/id3v2framefactory.cpp:132
 TagLib::ID3v2::Tag::parse (this=this@entry=0x26ed250, origData=...) at ../../taglib/mpeg/id3v2/id3v2tag.cpp:700

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in baloo (Ubuntu):
importance: Undecided → Medium
summary: - baloo_file_extractor crashed with SIGSEGV in
- TagLib::ByteVector::replace()
+ baloo_file_extractor crashed with SIGSEGV in memcpy()
tags: removed: need-amd64-retrace
Revision history for this message
Harald Sitter (apachelogger) wrote :

Hi there!

Thanks for reporting this bug! Your bug seems to be a problem with the KDE program itself, and not with our KDE packages. While we appreciate your issue, it would be better if it was tracked at https://bugs.kde.org, so that the KDE developers can deal with this speedily and have direct communication with you as the reporter for more effective debugging.

Thanks!

information type: Private → Public
Changed in baloo (Ubuntu):
status: New → Invalid
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.