https://bugs.kde.org/show_bug.cgi?id=335164
Bug ID: 335164 Summary: Crash while updating image metadata to database in tools->maint. all cores Classification: Unclassified Product: digikam Version: 4.0.0 Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Database Assignee: [hidden email] Reporter: [hidden email] digikam was compiled from git master on 5/21 (today). Splash screen says 4.1.0 Reproducible: Didn't try Steps to Reproduce: 1. tools->maint.->update metadata image to database 2. Do nothing while waiting for the crash 3. Actual Results: Crash Expected Results: database should have image metadata in it. -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
https://bugs.kde.org/show_bug.cgi?id=335164
--- Comment #1 from Jim Shipman <[hidden email]> --- Created attachment 86760 --> https://bugs.kde.org/attachment.cgi?id=86760&action=edit digikam log output from gdb. log from running digikam in gdb. -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
In reply to this post by James R. Shipman
https://bugs.kde.org/show_bug.cgi?id=335164
Christoph Feck <[hidden email]> changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|normal |crash -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
In reply to this post by James R. Shipman
https://bugs.kde.org/show_bug.cgi?id=335164
Gilles Caulier <[hidden email]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED CC| |[hidden email] Resolution|--- |BACKTRACE --- Comment #2 from Gilles Caulier <[hidden email]> --- I'm not sure if crash appear in DB. The gdb backtrace is uncomplete. you pass from thread 100 to 6. It miss data. Sound like backtrace is corrupted. Re-run digiKam in GDB as explained here to get a better backtrace : http://www.digikam.org/contrib -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
In reply to this post by James R. Shipman
https://bugs.kde.org/show_bug.cgi?id=335164
Jim Shipman <[hidden email]> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #86760|0 |1 is obsolete| | --- Comment #3 from Jim Shipman <[hidden email]> --- Created attachment 86762 --> https://bugs.kde.org/attachment.cgi?id=86762&action=edit New debug backtrace output -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
In reply to this post by James R. Shipman
https://bugs.kde.org/show_bug.cgi?id=335164
Jim Shipman <[hidden email]> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #86762|0 |1 is obsolete| | --- Comment #4 from Jim Shipman <[hidden email]> --- Created attachment 86764 --> https://bugs.kde.org/attachment.cgi?id=86764&action=edit Yet another backtrace - with debuginfo included digikam crashes very quickly. This is highly repeatable. -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
In reply to this post by James R. Shipman
https://bugs.kde.org/show_bug.cgi?id=335164
Gilles Caulier <[hidden email]> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|BACKTRACE |UPSTREAM --- Comment #5 from Gilles Caulier <[hidden email]> --- It crash in Exiv2 shared lib, not digiKam as well, probably when image are scanned at startup. (gdb) #0 0x00000035ec05f0e1 in __cxa_throw () from /usr/lib64/libstdc++.so.6 #1 0x00000033e6ee54a6 in Exiv2::ImageFactory::open(std::string const&) () from /usr/lib64/libexiv2.so.13 #2 0x00007ffff75e356a in KExiv2Iface::KExiv2::load (this=0x7fff800564a0, filePath=...) at /home/shipman/Downloads/dk/extra/libkexiv2/libkexiv2/kexiv2.cpp:298 #3 0x00007ffff6e54cf9 in Digikam::DMetadata::load (this=0x7fff800564a0, filePath=...) Please report this problem to Exiv2 project, and try to identify which image crash exiv2 to join file on your report Best Gilles Caulier -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
In reply to this post by James R. Shipman
https://bugs.kde.org/show_bug.cgi?id=335164
[hidden email] changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Database |Metadata-Engine -- You are receiving this mail because: You are the assignee for the bug. |
Free forum by Nabble | Edit this page |