[Digikam-devel] [digikam] [Bug 347753] surface freezes after some faces tagged

[Gilles Caulier]

https://bugs.kde.org/show_bug.cgi?id=347753

--- Comment #18 from Gilles Caulier <caulier.gilles at gmail.com> ---
Alan,

Look again the backtrace :

(gdb) bt
#0  0x00007ffff0f494c0 in __cxa_throw () from /usr/lib64/libstdc++.so.6
#1  0x00007fffee5cea56 in Exiv2::XmpProperties::nsInfo(std::string const&) ()
from /usr/lib64/libexiv2.so.13
#2  0x00007fffee5ceb30 in Exiv2::XmpProperties::ns(std::string const&) () from
/usr/lib64/libexiv2.so.13
#3  0x00007fffee5cf36b in Exiv2::XmpKey::Impl::decomposeKey(std::string const&)
() from /usr/lib64/libexiv2.so.13
#4  0x00007fffee5cf735 in Exiv2::XmpKey::XmpKey(std::string const&) () from
/usr/lib64/libexiv2.so.13
#5  0x00007ffff639d805 in KExiv2Iface::KExiv2::removeXmpTag(char const*, bool)
const () from /usr/lib64/libkexiv2.so.11

It look like Exiv2 debug symbols are not installed. So it's impossible to see
exactly where in Exiv2 code the problem appears.

I recommend : 

* to install Exiv2 debug package and try to get a better GDB backtrace.
* to catch exception directly in GDB before to run digiKam, as explained at
https://www.digikam.org/contrib

I suspect that Adobe XMP SDK generate an exception which is not catch by Exiv2
code. 

The previous test with Exiv2 CLI tool can be not enough. I suspect that CLI
interface check XMP tag to manage with M option before to do something in file
metadata.

Gilles

-- 
You are receiving this mail because:
You are the assignee for the bug.