[Digikam-devel] [Bug 128104] Digikam Crash when browsing photos in Image Editor

[Sebastian Röder]

> no, digiKam do not depand of Exiv2 0.10.0 especially. The code must
> still compatible with oldiers version.
>
> I just use Exiv2 0.10.0 because the library have been very improved.

I first want to track down this problem befor I switch from stable exiv2-0.9.1 
to exiv2-SVN to avoid a additional source of error. 

I have uninstalled and reinstalled exiv2-0.9.1 from Gentoo ebuild and the 
problem is still there. I do NOT have other exiv2 installs flying around. 
Here is another log + gdb bt: 

[New Thread -1518752848 (LWP 11852)]
digikam: Cannot parse EXIF metadata using Exiv2
QFile::open: No file name specified
QFile::open: No file name specified
digikam: /home/sero/photos/Test/letzte_vorstellung-0001.JPG : JPEG file 
identified
digikam: /home/sero/photos/Test/letzte_vorstellung-0002.JPG : JPEG file 
identified
digikam: /home/sero/photos/Test/letzte_vorstellung-0003.JPG : JPEG file 
identified
digikam: /home/sero/photos/Test/letzte_vorstellung-0004.JPG : JPEG file 
identified
digikam: /home/sero/photos/Test/letzte_vorstellung-0005.JPG : JPEG file 
identified
digikam: /home/sero/photos/Test/letzte_vorstellung-0006.JPG : JPEG file 
identified
Corrupt JPEG data: premature end of data segment
Unsupported marker type 0xfc
digikam: /home/sero/photos/Test/letzte_vorstellung-0007.JPG : JPEG file 
identified
digikam: /home/sero/photos/Test/letzte_vorstellung-0008.JPG : JPEG file 
identified
digikam: /home/sero/photos/Test/letzte_vorstellung-0009.JPG : JPEG file 
identified
*** glibc detected *** malloc(): memory corruption: 0x0866a0e0 ***

Program received signal SIGABRT, Aborted.
[Switching to Thread -1518752848 (LWP 11852)]
0xffffe410 in __kernel_vsyscall ()
(gdb) bt
#0  0xffffe410 in __kernel_vsyscall ()
#1  0xa60fb261 in raise () from /lib/tls/libc.so.6
#2  0xa60fc9f9 in abort () from /lib/tls/libc.so.6
#3  0xa612f09a in __fsetlocking () from /lib/tls/libc.so.6
#4  0xa6134fb7 in malloc_usable_size () from /lib/tls/libc.so.6
#5  0xa6135f2d in free () from /lib/tls/libc.so.6
#6  0xa61375e1 in malloc () from /lib/tls/libc.so.6
#7  0xa62bff9f in operator new ()
   from /usr/lib/gcc/i686-pc-linux-gnu/3.4.5/libstdc++.so.6
#8  0xa62c00cd in operator new[] ()
   from /usr/lib/gcc/i686-pc-linux-gnu/3.4.5/libstdc++.so.6
#9  0xa79720c9 in Exiv2::ExifData::updateRange ()
   from /usr/lib/libexiv2-0.9.1.so
#10 0xa79723ff in Exiv2::ExifData::updateEntries ()
   from /usr/lib/libexiv2-0.9.1.so
#11 0xa7972531 in Exiv2::ExifData::copy () from /usr/lib/libexiv2-0.9.1.so
#12 0xa7e86c0c in Digikam::DMetadata::getExif (this=0xa5799ba0)
    at dmetadata.cpp:96
#13 0xa7e786b8 in Digikam::DImgLoader::readMetadata (this=0x0, filePath=@0x0,
    ff=Digikam::DImg::NONE) at dimgloader.cpp:133
#14 0xa7e94336 in Digikam::JPEGLoader::load (this=0xa579a240,
    filePath=@0x859cc34, observer=0x859cc30) at jpegloader.cpp:101
#15 0xa7e6bf05 in Digikam::DImg::load (this=0xa579a370, filePath=@0x859cc34,
---Type <return> to continue, or q <return> to quit---
    observer=0x859cc30, rawDecodingSettings=Cannot access memory at address 
0x0
) at dimg.cpp:300
#16 0xa7e6f006 in DImg (this=0xa579a370, filePath=@0x0, observer=0x0,
    rawDecodingSettings=Cannot access memory at address 0x0
) at dimg.cpp:73
#17 0xa7e2369d in Digikam::SharedLoadingTask::execute (this=0x859cc28)
    at loadsavetask.cpp:162
#18 0xa7e1fd5b in Digikam::LoadSaveThread::run (this=0x8553108)
    at loadsavethread.cpp:134
#19 0xa68d7345 in QThreadInstance::start () from /usr/qt/3/lib/libqt-mt.so.3
#20 0xa63b5420 in start_thread () from /lib/tls/libpthread.so.0
#21 0xa618c39e in clone () from /lib/tls/libc.so.6


Hope this helps. I am pretty clueless how I should track this problem down. I 
guess I will manually compile exiv2-0.9.1 this evening to see if there is 
something wrong with the ebuild.

Regards,
Sero