https://bugs.kde.org/show_bug.cgi?id=393635
--- Comment #16 from caulier.gil...@gmail.com ---
Exiv2 team is serious ? The crash backtrace is clear :
#0 0x00007fec1165e186 in Exiv2::IptcData::printStructure(std::ostream&,
unsigned char const*, unsigned long, unsigned int) () from
/usr/lib/libexiv2.so.26
[Current thread is 1 (Thread 0x7feae8ff9700 (LWP 2696))]
(gdb) #0 0x00007fec1165e186 in Exiv2::IptcData::printStructure(std::ostream&,
unsigned char const*, unsigned long, unsigned int) () at
/usr/lib/libexiv2.so.26
#1 0x00007fec11658a20 in Exiv2::Image::printIFDStructure(Exiv2::BasicIo&,
std::ostream&, Exiv2::PrintStructureOption, unsigned int, bool, char, int) ()
at /usr/lib/libexiv2.so.26
#2 0x00007fec1165a558 in Exiv2::Image::printTiffStructure(Exiv2::BasicIo&,
std::ostream&, Exiv2::PrintStructureOption, int, unsigned long) () at
/usr/lib/libexiv2.so.26
#3 0x00007fec116d7115 in Exiv2::TiffImage::printStructure(std::ostream&,
Exiv2::PrintStructureOption, int) ()
at /usr/lib/libexiv2.so.26
#4 0x00007fec116d8bdb in Exiv2::TiffImage::readMetadata() () at
/usr/lib/libexiv2.so.26
#5 0x00007fec1b23e771 in Digikam::MetaEngine::load(QString const&) const () at
It's in Exiv2 code, not digiKam. The tiff parser and after the IPTC metadata
parser do something wrong with the image.
digiKam ask to Exiv2 to extract the image from standard IPTC preview tag
(typically a JPEG image). That all. The action is delegate to Exiv2, and
digiKam wait the data. The crash appear in the internal process from Exiv2.
It's not so far a digiKam crash.
Note: the warning come from Exiv2 and is just informative that some tags
structure cannot be handled properly. Exiv2 format the metadata container
accordingly and pass as well the data to the client application. That all... In
other word, this warning is not important for digiKam.
Gilles Caulier
--
You are receiving this mail because:
You are watching all bug changes.
