[Digikam-devel] Digikam Crash from Assert in libexiv2

Marcel Wiesweg marcel.wiesweg at gmx.de
Sat May 22 11:17:10 BST 2010


> I'm getting a digikam crash everytime I try to start up digikam (and it
> scans my files.)
> 
> It's in libexiv2 (SVN from today, May 21, 2010.)
> 
> I've tried looking some but would appreciate any pointers.  It looks
> like the write fails but I'm not quite sure what's being written (TIFF
> metadata to where?)
> 
> I have lots of diskspace both on the image and SQLite database
> filesystem (the same local disk.)
> 
> I added debug and see that the group name is CANON and sv is four more
> bytes than what was returned as having been written (I don't have that
> debug in this trace since I just updated exiv2.)
> 
> I suspect it's the same file each time but am not sure how to get the
> filename from inside the exiv2 code.
> 
> The last few lines of the stdout/stderr and stack backtrace are below.
> 
> If anyone has any suggestions for debugging this I'd appreciate it.

The best thing to do is isolating the file causing the crash.
Is any filename printed on the console, before the debug output you included 
in your mail?



More information about the Digikam-devel mailing list