[Digikam-devel] [Bug 136932] New: Access to a specific jpg photo crashed digikam

krienke at uni-koblenz.de krienke at uni-koblenz.de
Mon Nov 6 07:24:16 GMT 2006

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
           Summary: Access to a specific jpg  photo crashed digikam
           Product: digikam
           Version: 0.9.0-svn
          Platform: SuSE RPMs
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: general
        AssignedTo: digikam-devel kde org
        ReportedBy: krienke uni-koblenz de

Version:           0.9.0-svn (using KDE KDE 3.5.4)
Installed from:    SuSE RPMs
Compiler:          gcc 4.1.0 
OS:                Linux

I have a photo that first worked fine with dikikam. I did some editing on it, probably added a jpg comment to it in digikam which is stored inside the jpg. Now when digikam sees this file it crashes. Other tools like gwenview can however display it.

The debug info is:

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1240016160 (LWP 15201)]
[KCrash handler]
#5  Exiv2::getLong (buf=0x397900e8 <Address 0x397900e8 out of bounds>, 
    byteOrder=Exiv2::bigEndian) at types.cpp:196
#6  0xb79639af in Exiv2::getRational (
    buf=0x397900e8 <Address 0x397900e8 out of bounds>, 
    byteOrder=Exiv2::bigEndian) at types.cpp:202
#7  0xb791df4c in Exiv2::ValueType<std::pair<int, int> >::read (
    this=0x8160df8, buf=0x397900e8 <Address 0x397900e8 out of bounds>, 
    len=1786389032, byteOrder=Exiv2::bigEndian) at value.hpp:1014
#8  0xb79164de in Exiv2::Exifdatum::setValue (this=0xbfe026c0, e= 0x818b234, 
    byteOrder=Exiv2::bigEndian) at exif.cpp:193
#9  0xb79165c0 in Exifdatum (this=0xbfe026c0, e= 0x818b234, 
    byteOrder=<value optimized out>) at exif.cpp:97
#10 0xb791bba4 in Exiv2::ExifData::add (this=0x813d8cc, begin=
      {_M_current = 0x8187950}, end={_M_current = 0x818fd50}, 
    byteOrder=Exiv2::bigEndian) at exif.cpp:764
#11 0xb791c20e in Exiv2::ExifData::load (this=0x813d8cc, buf=0x817b3c8 "MM", 
    len=11509) at exif.cpp:596
#12 0xb793001b in Exiv2::JpegBase::readMetadata (this=0x813d8c0)
    at jpgimage.cpp:301
#13 0xb7eb457b in Digikam::DMetaLoader::loadWithExiv2 ()
   from /opt/kde3/lib/libdigikam.so.0
#14 0xb7eb50d4 in Digikam::JPEGMetaLoader::load ()
   from /opt/kde3/lib/libdigikam.so.0
#15 0xb7e9aa33 in Digikam::DMetadata::load ()
   from /opt/kde3/lib/libdigikam.so.0
#16 0xb7e9d420 in Digikam::DMetadata::DMetadata ()
   from /opt/kde3/lib/libdigikam.so.0
#17 0xb7cf3b10 in Digikam::ScanLib::storeItemInDatabase ()
   from /opt/kde3/lib/libdigikam.so.0
#18 0xb7cf5798 in Digikam::ScanLib::allFiles ()
   from /opt/kde3/lib/libdigikam.so.0
#19 0xb7cf5fd9 in Digikam::ScanLib::findMissingItems ()
   from /opt/kde3/lib/libdigikam.so.0
#20 0xb7cf696f in Digikam::ScanLib::startScan ()
   from /opt/kde3/lib/libdigikam.so.0
#21 0xb7c932af in Digikam::AlbumManager::setLibraryPath ()
   from /opt/kde3/lib/libdigikam.so.0
#22 0x0804a375 in main ()

The file can be read from 


More information about the Digikam-devel mailing list