https://bugs.kde.org/show_bug.cgi?id=406229
Nate Graham <n...@kde.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REPORTED |RESOLVED
Resolution|--- |UPSTREAM
--- Comment #5 from Nate Graham <n...@kde.org> ---
Relevant part of the backtrace:
#17 0x00007fd23bcada06 in Exiv2::TiffParser::decode(Exiv2::ExifData&,
Exiv2::IptcData&, Exiv2::XmpData&, unsigned char const*, unsigned int) () from
/usr/lib/x86_64-linux-gnu/libexiv2.so.26
#18 0x00007fd23bc29330 in Exiv2::ExifParser::decode(Exiv2::ExifData&, unsigned
char const*, unsigned int) () from /usr/lib/x86_64-linux-gnu/libexiv2.so.26
#19 0x00007fd23bc43170 in Exiv2::JpegBase::readMetadata() () from
/usr/lib/x86_64-linux-gnu/libexiv2.so.26
#20 0x00007fd24004d208 in KFileMetaData::Exiv2Extractor::extract
(this=0x5639d84966f0, result=0x7ffece28b320) at
./src/extractors/exiv2extractor.cpp:163
#21 0x00005639d6eb022f in Baloo::App::index (this=this@entry=0x7ffece28bac0,
tr=0x5639d8abbc80, url=..., id=id@entry=5642697968715777) at
./src/file/extractor/app.cpp:192
#22 0x00005639d6eb0b8e in Baloo::App::processNextFile (this=0x7ffece28bac0) at
./src/file/extractor/app.cpp:112
So Exiv2 first (correctly) tries the JPEG extractor, then switches to the TIFF
extractor for some reason, then crashes.
At this point it feels like the issue is in Exiv2 itself, not Baloo or
KFileMetadata, both of which have done their part as much as they're able. Can
you file a bug with the Exiv2 folks? The fully symbolicated backtrace you
attached will probably be very useful for them. Thanks!
--
You are receiving this mail because:
You are watching all bug changes.
