Exiv2 creates out of range exception with XMP data

Bug #1942799 reported by Isaac Carter
18
This bug affects 4 people
Affects Status Importance Assigned to Milestone
exiv2 (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Applying the latest update to Exiv2 in both Pix and gThumb, images that contain XMP data will crash the given application. The issue looks to be when Xmp data is not able to properly handle the call to "c_str()".

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in exiv2 (Ubuntu):
status: New → Confirmed
Revision history for this message
Heiko (heiko-bauke-snafu) wrote :

XMP data is commonly included in image metadata of images that have been exported from darktable. Opening such an image in gthumb causes a non-handled std::out_of_range exception in Exiv2::Xmpdatum::write. Finally, gthumb terminates with the message

terminate called after throwing an instance of 'std::out_of_range'
  what(): basic_string::at: __n (which is 19) >= this->size() (which is 19)

Revision history for this message
Isaac Carter (icarter1391) wrote :

The code in question for both Pix and gthumb looks to be one of the FOR loops in "exiv2_read_metadata" in exiv2-utils.cpp, where this line...

  md->print().c_str()

...creates the out of range exception.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.