shotwell crashed with SIGSEGV in Exiv2::DataValue::toLong()

[ketan]

Binary package hint: shotwell

I was importing my photos from fspot

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: shotwell 0.7.2-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic i686
Architecture: i386
Date: Wed Sep 29 15:05:35 2010
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/shotwell
InstallationMedia: Kubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100427.1)
ProcCmdline: shotwell
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x31dc11 <_ZNK5Exiv29DataValue6toLongEl+17>: movzbl (%edx,%eax,1),%eax
 PC (0x0031dc11) ok
 source "(%edx,%eax,1)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: shotwell
StacktraceTop:
 Exiv2::DataValue::toLong(long) const () from /usr/lib/libexiv2.so.6
 gexiv2_metadata_get_exif_tag_long () from /usr/lib/libgexiv2.so.0
 gexiv2_metadata_get_tag_long () from /usr/lib/libgexiv2.so.0
 photo_metadata_get_long ()
 photo_metadata_get_iso ()
Title: shotwell crashed with SIGSEGV in Exiv2::DataValue::toLong()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Jim Nelson (yorba-jim)]

This bug is related to http://trac.yorba.org/ticket/2514.

It's possible in Exiv2 to have an empty metadata tag. If it's accessed for its value, the library segfaults. The fix for the ticket I just mentioned was a quick patch for the reporter's specific problem and not a general solution.

Last night I committed a patch to our repository that implements a general solution (which is ticket http://trac.yorba.org/ticket/2551). If you want to try it, check it out and build and install it:

svn co svn://svn.yorba.org/gexiv2/trunk gexiv2

If not, the fix should be released in gexiv2 0.3.0.

[Jim Nelson (yorba-jim)]

This is available in gexiv2 0.2.2.