Bug 138300 - crash on startup with one user's collection
Summary: crash on startup with one user's collection
Status: RESOLVED WORKSFORME
Alias: None
Product: digikam
Classification: Applications
Component: Metadata-Engine (show other bugs)
Version: unspecified
Platform: Debian testing Linux
: NOR crash
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-12-03 16:54 UTC by Anton Pussep
Modified: 2017-08-10 19:48 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In: 0.9.0


Attachments
26 warnings while compiling digikam 0.9.0-RC2 (1.97 KB, text/plain)
2006-12-13 07:58 UTC, Anton Pussep
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Anton Pussep 2006-12-03 16:54:37 UTC
Version:           0.9.0~beta3-3 (using KDE KDE 3.5.5)
Installed from:    Debian testing/unstable Packages

When I start digikam with the collection of my user "anton" digikam crashes at startup. I also tried to run digikam from root's account with this collection and it crashed also. Unfortunately I don't know anything about the used plugins, but I have the Debian package "digikamimageplugins" installed!

KDE Backtrace:

(no debugging symbols found)
Using host libthread_db library "/lib/tls/libthread_db.so.1".
(no debugging symbols found)
/* EDIT: same for 35 times */
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1240421600 (LWP 3485)]
(no debugging symbols found)
/* EDIT: same for 24 times */
(no debugging symbols found)
[KCrash handler]
#5  0xb61aa2ad in mallopt () from /lib/tls/libc.so.6
#6  0xb61aa942 in free () from /lib/tls/libc.so.6
#7  0xb634b361 in operator delete () from /usr/lib/libstdc++.so.6
#8  0xb6327ecd in std::string::_Rep::_M_destroy ()
   from /usr/lib/libstdc++.so.6
#9  0xb7f2ca56 in Digikam::DMetadata::convertCommentValue ()
   from /usr/lib/libdigikam.so.0
#10 0xb7f32146 in Digikam::DMetadata::getImageComment ()
   from /usr/lib/libdigikam.so.0
#11 0xb7d9aa6d in Digikam::ScanLib::storeItemInDatabase ()
   from /usr/lib/libdigikam.so.0
#12 0xb7d9c0c9 in Digikam::ScanLib::allFiles () from /usr/lib/libdigikam.so.0
#13 0xb7d9c07c in Digikam::ScanLib::allFiles () from /usr/lib/libdigikam.so.0
#14 0xb7d9c903 in Digikam::ScanLib::findMissingItems ()
   from /usr/lib/libdigikam.so.0
#15 0xb7d9cb87 in Digikam::ScanLib::startScan () from /usr/lib/libdigikam.so.0
#16 0xb7d38758 in Digikam::AlbumManager::setLibraryPath ()
   from /usr/lib/libdigikam.so.0
#17 0x0804a36b in main ()
Comment 1 caulier.gilles 2006-12-03 16:57:58 UTC
Anto,

This problem have been already reported in this room. Please update digiKam to RC1 and Exiv2 library to 0.12 release. Try again and give us a feedback. Thanks in advance

Gilles Caulier
Comment 2 caulier.gilles 2006-12-12 09:28:04 UTC
Anto, 
 
This crash still reproductible using digiKam/DigikamImagePlugins 0.9.0-RC2 and  Exiv2 0.12 ? 
 
Thanks in advance for your feedback. 
 
Gilles Caulier 
Comment 3 Anton Pussep 2006-12-12 09:36:03 UTC
Hello Gilles,

I installed 0.9.0-RC1 from the Debian unstable repository yesterday (Exiv2 does not depend on it, so it is not installed at all). And it crashes with the very same result.

I will try to compile 0.9.0-RC2 tomorrow and report then.

Best regards,
Anton
Comment 4 caulier.gilles 2006-12-12 09:40:09 UTC
Thanks,

several bug have been fixed in Exiv2 0.12. digiKam 0.9.0-RC2 require this Exiv2 version now. Unforget to uninstall all Exiv2 release from your computer before to install 0.12. Also, cleanup all digikam/DigikamImagePlugins source code and then recompile/install all.

Gilles
Comment 5 Anton Pussep 2006-12-13 07:58:07 UTC
Created attachment 18911 [details]
26 warnings while compiling digikam 0.9.0-RC2
Comment 6 Anton Pussep 2006-12-13 07:59:42 UTC
Hello Gilles,

I compiled and installed Exiv 0.12 and digikam 0.9.0-RC2 today and everything seems to function very well. Thank you very much! Keep up the good work!

BTW, may be it's not unimportant, there have been some warnings during the compilation process. I attached the file with the warnings to this bug report:

http://bugs.kde.org/attachment.cgi?id=18911
Comment 7 caulier.gilles 2006-12-13 08:04:06 UTC
Anton,

Yes, i know the warning. It duing to dcraw::parse.c implementation ported by me in C++ witch is originaly a C-ANSI implementation. C++ compiler claim that something can be wrong, but in fact i won't touch the original implementation from dcraw author.

Also, in the future, this implementation will be removed. I will create a new shared libkdcraw library will be an interface to dcraw program witch will working like a library.

To resume, forget these warnings...

Gilles
Comment 8 Stefan Kooman 2008-04-06 16:36:33 UTC
DRKonqi output:

[?1034hUsing host libthread_db library "/lib64/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 0x2afda2f25e60 (LWP 16149)]
[KCrash handler]
#5  0x00002afda2c52f20 in memmove () from /lib64/libc.so.6
#6  0x00002afd9ac2ec4f in std::vector<unsigned char, std::allocator<unsigned char> >::_M_assign_aux<unsigned char const*> () from /usr/local/lib/libexiv2.so.2
#7  0x00002afd9ac2a1e4 in Exiv2::DataValue::read ()
   from /usr/local/lib/libexiv2.so.
2
#8  0x00002afd9ac22e79 in Exiv2::TiffReader::readTiffEntry ()
   from /usr/local/lib/libexiv2.so.2
#9  0x00002afd9ac23681 in Exiv2::TiffReader::visitMnEntry ()
   from /usr/local/lib/libexiv2.so.2
#10 0x00002afd9ac1da80 in Exiv2::TiffMnEntry::doAccept ()
   from /usr/local/lib/libexiv2.so.2
#11 0x00002afd9ac1dc3b in Exiv2::TiffDirectory::doAccept ()
   from /usr/local/lib/libexiv2.so.2
#12 0x00002afd9ac1db96 in Exiv2::TiffSubIfd::doAccept ()
   from /usr/local/lib/libexiv2.so.2
#13 0x00002afd9ac1dc3b in Exiv2::TiffDirectory::doAccept ()
   from /usr/local/lib/libexiv2.so.2
#14 0x00002afd9ac20b06 in Exiv2::TiffParser::decode ()
   from /usr/local/lib/libexiv2.so.2
#15 0x00002afd9ac1f850 in Exiv2::TiffImage::readMetadata ()
   from /usr/local/lib/libexiv2.so.2
#16 0x00002afd9a92a0a8 in KExiv2Iface::KExiv2::load ()
   from /opt/kde3/lib64/libkexiv2.so.3
#17 0x00002afd98753a99 in Digikam::DMetadata::load ()
   from /opt/kde3/lib64/libdigikam.so.0
#18 0x00002afd98642095 in Digikam::ScanLib::storeItemInDatabase ()
   from /opt/kde3/lib64/libdigikam.so.0
#19 0x00002afd9864420d in Digikam::ScanLib::allFiles ()
   from /opt/kde3/lib64/libdigikam.so.0
#20 0x00002afd986441ca in Digikam::ScanLib::allFiles ()
   from /opt/kde3/lib64/libdigikam.so.0
#21 0x00002afd986441ca in Digikam::ScanLib::allFiles ()
   from /opt/kde3/lib64/libdigikam.so.0
#22 0x00002afd9864496a in Digikam::ScanLib::findMissingItems ()
   from /opt/kde3/lib64/libdigikam.so.0
#23 0x00002afd98644bff in Digikam::ScanLib::startScan ()
   from /opt/kde3/lib64/libdigikam.so.0
#24 0x00002afd98603a3d in Digikam::AlbumManager::setLibraryPath ()
   from /opt/kde3/lib64/libdigikam.so.0
#25 0x00002afd985caa17 in Digikam::DigikamApp::DigikamApp ()
   from /opt/kde3/lib64/libdigikam.so.0
#26 0x0000000000403385 in main ()

Compiled digikam-0.94-beta2 from source. Compiled the following libs and plugins:
kipi-plugins-0.1.5
libkipi-0.1.5
jasper-1.900.1
libkdcraw-0.1.4
libkexiv2-0.1.6

Installed (rpm) the folliwing deps:
gphoto-2.4.0-25
libgphoto2-devel-2.4.0-25.2
libgphoto2-2.4.0-25.2
Comment 9 caulier.gilles 2008-04-06 22:46:32 UTC
Crash appear in Exiv2 shared lib, not digiKam. Check if you haven't
both version instaled on your system at the same time.

Gilles Caulier


6 Apr 2008 14:36:35 -0000, Stefan Kooman <stefan@kooman.org>:
[bugs.kde.org quoted mail]