Hi,
just tried to compile digikam 0.9 from svn. I made every step according to the instructions on the digikam website. After checking out I started compiling in the graphics directory with make -f Makefile.cvs Here is the result # make -f Makefile.cvs This Makefile is only for the CVS repository This will be deleted before making the distribution ./admin/cvs.sh: line 33: --version: command not found *** AUTOCONF NOT FOUND!. *** KDE requires autoconf 2.53 or newer make[1]: *** [cvs] Fehler 1 make: *** [all] Fehler 2 I have definitely autoconf version 2.60a-1 installed (in /usr/bin). I needed it yesterday for compiling from tarballs (cf previous posts). If I disregard the error and go on with ./configure I get bash: ./configure: File or directory not found (literally translated from German) What do I do now? Greetings Udo _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Le Mardi 29 Août 2006 12:29 AM, efpost a écrit :
> Hi, > > just tried to compile digikam 0.9 from svn. I made every step according > to the instructions on the digikam website. > After checking out I started compiling in the graphics directory with > make -f Makefile.cvs > > Here is the result > > # make -f Makefile.cvs > This Makefile is only for the CVS repository > This will be deleted before making the distribution > > ./admin/cvs.sh: line 33: --version: command not found > *** AUTOCONF NOT FOUND!. > *** KDE requires autoconf 2.53 or newer > make[1]: *** [cvs] Fehler 1 > make: *** [all] Fehler 2 > > I have definitely autoconf version 2.60a-1 installed (in /usr/bin). I > needed it yesterday for compiling from tarballs (cf previous posts). > > If I disregard the error and go on with ./configure I get > bash: ./configure: File or directory not found (literally translated > from German) > > What do I do now? > Under mandriva 2006, i use : [gilles@portable-gc apps]$ autoconf --version autoconf (GNU Autoconf) 2.59 Written by David J. MacKenzie and Akim Demaille. ... ...without problems. Also, i recommend you to look the README file about depencies. Gilles _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
It's done. Studying the README file clarified the situation. Not AUTOCONF was missing, but AUTOMAKE. After installing automake 1.9 the compilation went just fine.Le Mardi 29 Août 2006 12:29 AM, efpost a écrit :Hi, just tried to compile digikam 0.9 from svn. I made every step according to the instructions on the digikam website. After checking out I started compiling in the graphics directory with make -f Makefile.cvs Here is the result # make -f Makefile.cvs This Makefile is only for the CVS repository This will be deleted before making the distribution ./admin/cvs.sh: line 33: --version: command not found *** AUTOCONF NOT FOUND!. *** KDE requires autoconf 2.53 or newer make[1]: *** [cvs] Fehler 1 make: *** [all] Fehler 2 I have definitely autoconf version 2.60a-1 installed (in /usr/bin). I needed it yesterday for compiling from tarballs (cf previous posts). If I disregard the error and go on with ./configure I get bash: ./configure: File or directory not found (literally translated from German) What do I do now?Under mandriva 2006, i use : [gilles@portable-gc apps]$ autoconf --version autoconf (GNU Autoconf) 2.59 Written by David J. MacKenzie and Akim Demaille. ... ...without problems. Also, i recommend you to look the README file about depencies. Gilles _______________________________________________ Digikam-users mailing list BUT: digikam 0.9 keeps crashing. I started digikam clean (no digikamrc, no digikam.db) and set as the database directory an existing directory with subdirectories and images (as described in my previous posts) Here is the output from KDE crash handler: ------------- Using host libthread_db library "/lib/tls/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1240873280 (LWP 14916)] [KCrash handler] #5 0xb613e2ad in mallopt () from /lib/tls/libc.so.6 #6 0xb613e942 in free () from /lib/tls/libc.so.6 #7 0xb62e24e1 in operator delete () from /usr/lib/libstdc++.so.6 #8 0xb62be1ed in std::string::_Rep::_M_destroy () from /usr/lib/libstdc++.so.6 #9 0xb62c0d58 in std::basic_string<char, std::char_traits<char>, std::allocator<char> >::~basic_string () from /usr/lib/libstdc++.so.6 #10 0xb7eb9df7 in Digikam::DMetadata::convertCommentValue ( exifDatum=@0x815d70c) at dmetadata.cpp:1092 #11 0xb7ebaacd in Digikam::DMetadata::getImageComment (this=0xbf8ae518) at dmetadata.cpp:936 #12 0xb7d4a0b9 in Digikam::ScanLib::storeItemInDatabase (this=0xbf8ae878, albumURL=@0xbf8ae5b8, filename=@0xbf8ae604, albumID=2) at scanlib.cpp:397 #13 0xb7d4a616 in Digikam::ScanLib::allFiles (this=0xbf8ae878, directory=@0xbf8ae710) at scanlib.cpp:350 #14 0xb7d4a728 in Digikam::ScanLib::allFiles (this=0xbf8ae878, directory=@0xbf8ae7b0) at scanlib.cpp:355 #15 0xb7d4b2f8 in Digikam::ScanLib::findMissingItems (this=0xbf8ae878) at scanlib.cpp:191 #16 0xb7d4b87d in Digikam::ScanLib::startScan (this=0xbf8ae878) at scanlib.cpp:91 #17 0xb7ceb0d0 in Digikam::AlbumManager::setLibraryPath (this=0x8129100, path=@0xbf8aea78) at albummanager.cpp:289 #18 0x0804a85c in main (argc=-1208526040, argv=0xb6208420) at main.cpp:243 ------------------ Could somebody please point me into the right direction. Greetings Udo _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Le Mardi 29 Août 2006 14:03, efpost a écrit :
> Caulier Gilles schrieb: > >Le Mardi 29 Août 2006 12:29 AM, efpost a écrit : > >>Hi, > >> > >>just tried to compile digikam 0.9 from svn. I made every step according > >>to the instructions on the digikam website. > >>After checking out I started compiling in the graphics directory with > >>make -f Makefile.cvs > >> > >>Here is the result > >> > >> # make -f Makefile.cvs > >>This Makefile is only for the CVS repository > >>This will be deleted before making the distribution > >> > >>./admin/cvs.sh: line 33: --version: command not found > >>*** AUTOCONF NOT FOUND!. > >>*** KDE requires autoconf 2.53 or newer > >>make[1]: *** [cvs] Fehler 1 > >>make: *** [all] Fehler 2 > >> > >>I have definitely autoconf version 2.60a-1 installed (in /usr/bin). I > >>needed it yesterday for compiling from tarballs (cf previous posts). > >> > >>If I disregard the error and go on with ./configure I get > >>bash: ./configure: File or directory not found (literally translated > >>from German) > >> > >>What do I do now? > > > >Under mandriva 2006, i use : > > > >[gilles@portable-gc apps]$ autoconf --version > >autoconf (GNU Autoconf) 2.59 > >Written by David J. MacKenzie and Akim Demaille. > >... > > > >...without problems. Also, i recommend you to look the README file about > >depencies. > > > >Gilles > >_______________________________________________ > >Digikam-users mailing list > > It's done. Studying the README file clarified the situation. Not > AUTOCONF was missing, but AUTOMAKE. After installing automake 1.9 the > compilation went just fine. > > BUT: digikam 0.9 keeps crashing. > I started digikam clean (no digikamrc, no digikam.db) and set as the > database directory an existing directory with subdirectories and images > (as described in my previous posts) > Here is the output from KDE crash handler: > > ------------- > Using host libthread_db library "/lib/tls/libthread_db.so.1". > [Thread debugging using libthread_db enabled] > [New Thread -1240873280 (LWP 14916)] > [KCrash handler] > #5 0xb613e2ad in mallopt () from /lib/tls/libc.so.6 > #6 0xb613e942 in free () from /lib/tls/libc.so.6 > #7 0xb62e24e1 in operator delete () from /usr/lib/libstdc++.so.6 > #8 0xb62be1ed in std::string::_Rep::_M_destroy () > from /usr/lib/libstdc++.so.6 > #9 0xb62c0d58 in std::basic_string<char, std::char_traits<char>, > std::allocator<char> >::~basic_string () from /usr/lib/libstdc++.so.6 > #10 0xb7eb9df7 in Digikam::DMetadata::convertCommentValue ( > exifDatum=@0x815d70c) at dmetadata.cpp:1092 > #11 0xb7ebaacd in Digikam::DMetadata::getImageComment (this=0xbf8ae518) > at dmetadata.cpp:936 > #12 0xb7d4a0b9 in Digikam::ScanLib::storeItemInDatabase (this=0xbf8ae878, > albumURL=@0xbf8ae5b8, filename=@0xbf8ae604, albumID=2) at > scanlib.cpp:397 > #13 0xb7d4a616 in Digikam::ScanLib::allFiles (this=0xbf8ae878, > directory=@0xbf8ae710) at scanlib.cpp:350 > #14 0xb7d4a728 in Digikam::ScanLib::allFiles (this=0xbf8ae878, > directory=@0xbf8ae7b0) at scanlib.cpp:355 > #15 0xb7d4b2f8 in Digikam::ScanLib::findMissingItems (this=0xbf8ae878) > at scanlib.cpp:191 > #16 0xb7d4b87d in Digikam::ScanLib::startScan (this=0xbf8ae878) > at scanlib.cpp:91 > #17 0xb7ceb0d0 in Digikam::AlbumManager::setLibraryPath (this=0x8129100, > path=@0xbf8aea78) at albummanager.cpp:289 > #18 0x0804a85c in main (argc=-1208526040, argv=0xb6208420) at main.cpp:243 > ------------------ > > Could somebody please point me into the right direction. Yes, the other part relevent of this crash is Exiv2 library. Here i use Exiv2 source code from svn repository (i'm also an Exiv2 developper), not the last stable release 0.10... Look here for instructions to download and compile Exiv2 from svn : http://www.exiv2.org/download.html Gilles _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Well, that didn't help. I have compiled and installed exiv2 from SVN. Then I started digikam and faced the same Problems.Le Mardi 29 Août 2006 14:03, efpost a écrit :Caulier Gilles schrieb:Le Mardi 29 Août 2006 12:29 AM, efpost a écrit :Hi, just tried to compile digikam 0.9 from svn. I made every step according to the instructions on the digikam website. After checking out I started compiling in the graphics directory with make -f Makefile.cvs Here is the result # make -f Makefile.cvs This Makefile is only for the CVS repository This will be deleted before making the distribution ./admin/cvs.sh: line 33: --version: command not found *** AUTOCONF NOT FOUND!. *** KDE requires autoconf 2.53 or newer make[1]: *** [cvs] Fehler 1 make: *** [all] Fehler 2 I have definitely autoconf version 2.60a-1 installed (in /usr/bin). I needed it yesterday for compiling from tarballs (cf previous posts). If I disregard the error and go on with ./configure I get bash: ./configure: File or directory not found (literally translated>from German)What do I do now?Under mandriva 2006, i use : [gilles@portable-gc apps]$ autoconf --version autoconf (GNU Autoconf) 2.59 Written by David J. MacKenzie and Akim Demaille. ... ...without problems. Also, i recommend you to look the README file about depencies. Gilles _______________________________________________ Digikam-users mailing listIt's done. Studying the README file clarified the situation. Not AUTOCONF was missing, but AUTOMAKE. After installing automake 1.9 the compilation went just fine. BUT: digikam 0.9 keeps crashing. I started digikam clean (no digikamrc, no digikam.db) and set as the database directory an existing directory with subdirectories and images (as described in my previous posts) Here is the output from KDE crash handler: ------------- Using host libthread_db library "/lib/tls/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1240873280 (LWP 14916)] [KCrash handler] #5 0xb613e2ad in mallopt () from /lib/tls/libc.so.6 #6 0xb613e942 in free () from /lib/tls/libc.so.6 #7 0xb62e24e1 in operator delete () from /usr/lib/libstdc++.so.6 #8 0xb62be1ed in std::string::_Rep::_M_destroy () from /usr/lib/libstdc++.so.6 #9 0xb62c0d58 in std::basic_string<char, std::char_traits<char>, std::allocator<char> >::~basic_string () from /usr/lib/libstdc++.so.6 #10 0xb7eb9df7 in Digikam::DMetadata::convertCommentValue ( exifDatum=@0x815d70c) at dmetadata.cpp:1092 #11 0xb7ebaacd in Digikam::DMetadata::getImageComment (this=0xbf8ae518) at dmetadata.cpp:936 #12 0xb7d4a0b9 in Digikam::ScanLib::storeItemInDatabase (this=0xbf8ae878, albumURL=@0xbf8ae5b8, filename=@0xbf8ae604, albumID=2) at scanlib.cpp:397 #13 0xb7d4a616 in Digikam::ScanLib::allFiles (this=0xbf8ae878, directory=@0xbf8ae710) at scanlib.cpp:350 #14 0xb7d4a728 in Digikam::ScanLib::allFiles (this=0xbf8ae878, directory=@0xbf8ae7b0) at scanlib.cpp:355 #15 0xb7d4b2f8 in Digikam::ScanLib::findMissingItems (this=0xbf8ae878) at scanlib.cpp:191 #16 0xb7d4b87d in Digikam::ScanLib::startScan (this=0xbf8ae878) at scanlib.cpp:91 #17 0xb7ceb0d0 in Digikam::AlbumManager::setLibraryPath (this=0x8129100, path=@0xbf8aea78) at albummanager.cpp:289 #18 0x0804a85c in main (argc=-1208526040, argv=0xb6208420) at main.cpp:243 ------------------ Could somebody please point me into the right direction.Yes, the other part relevent of this crash is Exiv2 library. Here i use Exiv2 source code from svn repository (i'm also an Exiv2 developper), not the last stable release 0.10... Look here for instructions to download and compile Exiv2 from svn : http://www.exiv2.org/download.html Gilles _______________________________________________ Digikam-users mailing list --> Kcrash handler gives the following (more or less the same as previously): Using host libthread_db library "/lib/tls/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1240766784 (LWP 2784)] [KCrash handler] #5 0xb61582ad in mallopt () from /lib/tls/libc.so.6 #6 0xb6158942 in free () from /lib/tls/libc.so.6 #7 0xb62fc4e1 in operator delete () from /usr/lib/libstdc++.so.6 #8 0xb62d81ed in std::string::_Rep::_M_destroy () from /usr/lib/libstdc++.so.6 #9 0xb62dad58 in std::basic_string<char, std::char_traits<char>, std::allocator<char> >::~basic_string () from /usr/lib/libstdc++.so.6 #10 0xb7edbdf7 in Digikam::DMetadata::convertCommentValue ( exifDatum=@0x8159504) at dmetadata.cpp:1092 #11 0xb7edcacd in Digikam::DMetadata::getImageComment (this=0xbffb9418) at dmetadata.cpp:936 #12 0xb7d6c0b9 in Digikam::ScanLib::storeItemInDatabase (this=0xbffb9778, albumURL=@0xbffb94b8, filename=@0xbffb9504, albumID=2) at scanlib.cpp:397 #13 0xb7d6c616 in Digikam::ScanLib::allFiles (this=0xbffb9778, directory=@0xbffb9610) at scanlib.cpp:350 #14 0xb7d6c728 in Digikam::ScanLib::allFiles (this=0xbffb9778, directory=@0xbffb96b0) at scanlib.cpp:355 #15 0xb7d6d2f8 in Digikam::ScanLib::findMissingItems (this=0xbffb9778) at scanlib.cpp:191 #16 0xb7d6d87d in Digikam::ScanLib::startScan (this=0xbffb9778) at scanlib.cpp:91 #17 0xb7d0d0d0 in Digikam::AlbumManager::setLibraryPath (this=0x81291f8, path=@0xbffb9978) at albummanager.cpp:289 #18 0x0804a85c in main (argc=-1208386776, argv=0xb6222420) at main.cpp:243 What now? Udo _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Le Mardi 29 Août 2006 17:03, efpost a écrit :
> Gilles Caulier schrieb: > >Le Mardi 29 Août 2006 14:03, efpost a écrit : > >>Caulier Gilles schrieb: > >>>Le Mardi 29 Août 2006 12:29 AM, efpost a écrit : > >>>>Hi, > >>>> > >>>>just tried to compile digikam 0.9 from svn. I made every step according > >>>>to the instructions on the digikam website. > >>>>After checking out I started compiling in the graphics directory with > >>>>make -f Makefile.cvs > >>>> > >>>>Here is the result > >>>> > >>>> # make -f Makefile.cvs > >>>>This Makefile is only for the CVS repository > >>>>This will be deleted before making the distribution > >>>> > >>>>./admin/cvs.sh: line 33: --version: command not found > >>>>*** AUTOCONF NOT FOUND!. > >>>>*** KDE requires autoconf 2.53 or newer > >>>>make[1]: *** [cvs] Fehler 1 > >>>>make: *** [all] Fehler 2 > >>>> > >>>>I have definitely autoconf version 2.60a-1 installed (in /usr/bin). I > >>>>needed it yesterday for compiling from tarballs (cf previous posts). > >>>> > >>>>If I disregard the error and go on with ./configure I get > >>>>bash: ./configure: File or directory not found (literally translated > >>>> > >>>> > >>>>from German) > >>>> > >>>> > >>>>What do I do now? > >>> > >>>Under mandriva 2006, i use : > >>> > >>>[gilles@portable-gc apps]$ autoconf --version > >>>autoconf (GNU Autoconf) 2.59 > >>>Written by David J. MacKenzie and Akim Demaille. > >>>... > >>> > >>>...without problems. Also, i recommend you to look the README file about > >>>depencies. > >>> > >>>Gilles > >>>_______________________________________________ > >>>Digikam-users mailing list > >> > >>It's done. Studying the README file clarified the situation. Not > >>AUTOCONF was missing, but AUTOMAKE. After installing automake 1.9 the > >>compilation went just fine. > >> > >>BUT: digikam 0.9 keeps crashing. > >>I started digikam clean (no digikamrc, no digikam.db) and set as the > >>database directory an existing directory with subdirectories and images > >>(as described in my previous posts) > >>Here is the output from KDE crash handler: > >> > >>------------- > >>Using host libthread_db library "/lib/tls/libthread_db.so.1". > >>[Thread debugging using libthread_db enabled] > >>[New Thread -1240873280 (LWP 14916)] > >>[KCrash handler] > >>#5 0xb613e2ad in mallopt () from /lib/tls/libc.so.6 > >>#6 0xb613e942 in free () from /lib/tls/libc.so.6 > >>#7 0xb62e24e1 in operator delete () from /usr/lib/libstdc++.so.6 > >>#8 0xb62be1ed in std::string::_Rep::_M_destroy () > >> from /usr/lib/libstdc++.so.6 > >>#9 0xb62c0d58 in std::basic_string<char, std::char_traits<char>, > >>std::allocator<char> >::~basic_string () from /usr/lib/libstdc++.so.6 > >>#10 0xb7eb9df7 in Digikam::DMetadata::convertCommentValue ( > >> exifDatum=@0x815d70c) at dmetadata.cpp:1092 > >>#11 0xb7ebaacd in Digikam::DMetadata::getImageComment (this=0xbf8ae518) > >> at dmetadata.cpp:936 > >>#12 0xb7d4a0b9 in Digikam::ScanLib::storeItemInDatabase (this=0xbf8ae878, > >> albumURL=@0xbf8ae5b8, filename=@0xbf8ae604, albumID=2) at > >>scanlib.cpp:397 > >>#13 0xb7d4a616 in Digikam::ScanLib::allFiles (this=0xbf8ae878, > >> directory=@0xbf8ae710) at scanlib.cpp:350 > >>#14 0xb7d4a728 in Digikam::ScanLib::allFiles (this=0xbf8ae878, > >> directory=@0xbf8ae7b0) at scanlib.cpp:355 > >>#15 0xb7d4b2f8 in Digikam::ScanLib::findMissingItems (this=0xbf8ae878) > >> at scanlib.cpp:191 > >>#16 0xb7d4b87d in Digikam::ScanLib::startScan (this=0xbf8ae878) > >> at scanlib.cpp:91 > >>#17 0xb7ceb0d0 in Digikam::AlbumManager::setLibraryPath (this=0x8129100, > >> path=@0xbf8aea78) at albummanager.cpp:289 > >>#18 0x0804a85c in main (argc=-1208526040, argv=0xb6208420) at > >> main.cpp:243 ------------------ > >> > >>Could somebody please point me into the right direction. > > > >Yes, the other part relevent of this crash is Exiv2 library. > > > >Here i use Exiv2 source code from svn repository (i'm also an Exiv2 > >developper), not the last stable release 0.10... > > > >Look here for instructions to download and compile Exiv2 from svn : > > > >http://www.exiv2.org/download.html > > > >Gilles > >_______________________________________________ > >Digikam-users mailing list > > Well, that didn't help. I have compiled and installed exiv2 from SVN. > Then I started digikam Oups, i have forget to said than before to install Exiv2 from svn, you need to uninstall Exiv2 0.10.0, else nothing will change in digiKam. After that, install Exiv2-svn, perform a "make distcleanup" in root digiKam source forder and rebuild all using make -f Makefile.cvs; ./configure ---enable-debug=full; make... Gilles _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
I had Exiv2 uninstalled already before installing the svn-version. Doing "make distcleanup" in console gives: make: *** Keine Regel, um >distcleanup> zu erstellen. Schluss. (Translation: No rule to generate/make distcleanup. End.) I think, I will deinstall everything und start from scratch with svn. Udo _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Le Mercredi 30 Août 2006 19:24, efpost a écrit :
> Gilles Caulier schrieb: > >>Well, that didn't help. I have compiled and installed exiv2 from SVN. > >>Then I started digikam > > > >Oups, i have forget to said than before to install Exiv2 from svn, you > > need to uninstall Exiv2 0.10.0, else nothing will change in digiKam. > > > >After that, install Exiv2-svn, perform a "make distcleanup" in root > > digiKam source forder and rebuild all using make -f Makefile.cvs; > > ./configure ---enable-debug=full; make... > > > >Gilles > >_______________________________________________ > >Digikam-users mailing list > >[hidden email] > >https://mail.kde.org/mailman/listinfo/digikam-users > > I had Exiv2 uninstalled already before installing the svn-version. > > Doing "make distcleanup" in console gives: > > make: *** Keine Regel, um >distcleanup> zu erstellen. Schluss. > (Translation: No rule to generate/make distcleanup. End.) > > I think, I will deinstall everything und start from scratch with svn. > > Udo Udo, If the bug do not disapear, please give me a sample picture from your camera. In fact the crash is relevant of comments extraction at digiKam startup. Comments are embeded to JPEG pictures by camera like exif comments, Makernote comments, IPTC caption, or JFIF comments. digiKam try to extract this string and put it to database to improve speedup searching from gui. The comments are encoding from camera is the hell, especially with JFIF comments section from JPEG. Nothing is very clear about the language encoding (if all use UTF8, all will be simple (:=)))) In the past, before 0.9.0-beta1, we have already found some picture witch crash digiKam exactly like you have on your computer (Nikon and Minolta if i remember). In digiKam, the part witch try to find the right encoding format can be uncomplete and can crash... Try to find the picture releavant of your problem and send me it by private mail (not ML). Thanks in advance for your patience. Gilles _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
In reply to this post by efpost
Alas digikam keeps crashing. I started the whole process from scratch. Any part of the previous installation had been removed. I even downloaded the svn -files anew. First I compiled exiv2 from svn. Everything went ok. Secondly I compiled digikam + digikamimageplugins from svn. Again everything went fine. Then I started digikam clean (without digikamrc) and entered an existing directory ("~/pictures" with subdir "2006" including about 200 images) as database-directory. Digikam crashed immediately with exactly the same traceback output as before: ------------------ Using host libthread_db library "/lib/tls/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1240701248 (LWP 17445)] [KCrash handler] #5 0xb61682ad in mallopt () from /lib/tls/libc.so.6 #6 0xb6168942 in free () from /lib/tls/libc.so.6 #7 0xb630c4e1 in operator delete () from /usr/lib/libstdc++.so.6 #8 0xb62e81ed in std::string::_Rep::_M_destroy () from /usr/lib/libstdc++.so.6 #9 0xb62ead58 in std::basic_string<char, std::char_traits<char>, std::allocator<char> >::~basic_string () from /usr/lib/libstdc++.so.6 #10 0xb7ef1e13 in Digikam::DMetadata::convertCommentValue ( exifDatum=@0x815bd4c) at dmetadata.cpp:1092 #11 0xb7ef2ae9 in Digikam::DMetadata::getImageComment (this=0xbfa44ea8) at dmetadata.cpp:936 #12 0xb7d7f579 in Digikam::ScanLib::storeItemInDatabase (this=0xbfa45208, albumURL=@0xbfa44f48, filename=@0xbfa44f94, albumID=2) at scanlib.cpp:398 #13 0xb7d7fad6 in Digikam::ScanLib::allFiles (this=0xbfa45208, directory=@0xbfa450a0) at scanlib.cpp:351 #14 0xb7d7fbe8 in Digikam::ScanLib::allFiles (this=0xbfa45208, directory=@0xbfa45140) at scanlib.cpp:356 #15 0xb7d807b8 in Digikam::ScanLib::findMissingItems (this=0xbfa45208) at scanlib.cpp:192 #16 0xb7d80d3d in Digikam::ScanLib::startScan (this=0xbfa45208) at scanlib.cpp:91 #17 0xb7d20190 in Digikam::AlbumManager::setLibraryPath (this=0x8129270, path=@0xbfa45408) at albummanager.cpp:289 #18 0x0804a85c in main (argc=-1208294136, argv=0xb6232420) at main.cpp:243Using host libthread_db library "/lib/tls/libthread_db.so.1". ------------------------------ I've run out of ideas. Udo _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Free forum by Nabble | Edit this page |