Version: 0.10.0 (using 4.2.00 (KDE 4.2.0), Gentoo) Compiler: i686-pc-linux-gnu-gcc OS: Linux (i686) release 2.6.28-gentoo-r2 Hi. I'm can't provide exactly TC to reproduce that bug, but it often happens to me, when i navigating through my raw files collection (cr2 from canon 30d camera). My TC: 1) Open digikam 2) Just navigate through images inside single album (even not editing anything). Juts navigating using keyboard arrows or mouse. 3) Open any image using F4 and close window after image is fully loaded. 4) Navigate through images inside current album. On step 4 - digikam craches often for me. digikam is compiled from SVN today morning.
Crash report: http://pastebin.com/m666e3ab2 Full console output: http://pastebin.com/m340a9cac
The only string from digiKam is : #7 0xb7133f9b in Digikam::LoadSaveThread::run () from /usr/kde/4.2/lib/libdigikamcore.so.1 All the rest is on libstdc++ Marcel, your viewpoint ? Gilles Caulier
The backtrace is without digikam debug info. Additionally, two of the threads have strangely broken backtrace that seem to be reversed. I cant even tell where it begins. Dont know why there is not digikam debug info in a self-compiled binary. Anyway, I would recommend to compile with debug info (so that digikam lines in the bt dont have ??, but method and source file location), run digikam from inside gdb (gdb digikam -> run) and try to provoke the crash.
Valery, What's news about this entry. It still valid ? Gilles Caulier
Hi Gilles, I can't reproduce this bug anymore, so, I'm changing its status to RESOLVED.