Version: unknown (using 3.5.8, compiled sources) Compiler: Target: i586-mandriva-linux-gnu OS: Linux (i686) release 2.6.18.8.tex5 show photo crashes In settings window . After changing settings. the OK button does not enable all you can chose is Cancel. Then Showphoto crashed (no debugging symbols found) Using host libthread_db library "/lib/i686/libthread_db.so.1". (no debugging symbols found) `shared object read from target memory' has disappeared; keeping its symbols. (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1239598208 (LWP 1760)] [New Thread -1243784288 (LWP 1762)] [KCrash handler] #6 0xb624409a in malloc_usable_size () from /lib/i686/libc.so.6 #7 0xb6245adf in mallopt () from /lib/i686/libc.so.6 #8 0xb6245f23 in free () from /lib/i686/libc.so.6 #9 0xb63e64f1 in operator delete () from /usr/lib/libstdc++.so.6 #10 0xb63e654d in operator delete[] () from /usr/lib/libstdc++.so.6 #11 0xb73ce135 in KZoneAllocator::~KZoneAllocator () from /usr/lib/libkdecore.so.4 #12 0xb73ce19d in KZoneAllocator::~KZoneAllocator () from /usr/lib/libkdecore.so.4 #13 0xb620bec6 in __cxa_finalize () from /lib/i686/libc.so.6 #14 0xb73a3533 in ?? () from /usr/lib/libkdecore.so.4 #15 0xb751ba4c in _fini () from /usr/lib/libkdecore.so.4 #16 0xb7fbc570 in _dl_fini () at dl-fini.c:248 #17 0xb620bc29 in exit () from /lib/i686/libc.so.6 #18 0xb61f6764 in __libc_start_main () from /lib/i686/libc.so.6 #19 0x08073761 in ?? ()
Hi Scott, which version of digikam/showfoto are you using? Unfortunately, the above backtrace is cannot be used to track down the problem, because there are no debugging symbols (message "(no debugging symbols found)") related to digikam/showfoto. For this you have to compile digikam and enable debugging, see http://www.digikam.org/?q=contrib under the heading "If you are experiencing crashes with digiKam". Maybe there are already packages for mandriva, which provide a debug build? Best, Arnd
0.7.0
scott, I'm using Mandriva 2008.0 to develop digiKam/Showfoto. Crash is not reproductible here. Of course i compile all by hand. I suspect a packaging problem... Gilles Caulier
Scott, Try to use valgrind against current showfoto implementation from svn like this : valgrind --tool=memcheck --leak-check=full --error-limit=no showfoto It do not report any fatal error about wrong memory management in showfoto when i use settings dialog. I cannot reproduce the crash here. I can see few problem in Qt or kdelibs but not from showfoto implementation. Please just run showfoto under valgrind, open settings dialog, and close it. Just report the console backtrace in this file for investiguations. Thanks in advance Gilles Caulier
What about this bugreport? Still valid? Otherwise we should close it.
Since nobody can confirm this one here we should close it... I will do so for now. Scott, we can reopen this one if you really think so, but you should also try to use the new version of showFoto provided by your linux distribution. Andi
Andi, Without a suitable backtrace, it impossible to hack something. So, i'm agree to close it as Work for me Gilles
Ive just been to busy.. I dont think there is newer ver of showfoto for pclos yet