Summary: | Crash when importing Pentax DNG file | ||
---|---|---|---|
Product: | [Applications] digikam | Reporter: | Hombre <natureh.510> |
Component: | Metadata-Raw | Assignee: | Digikam Developers <digikam-bugs-null> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | caulier.gilles, freisim93, metzpinguin |
Priority: | NOR | ||
Version: | 5.7.0 | ||
Target Milestone: | --- | ||
Platform: | Microsoft Windows | ||
OS: | Microsoft Windows | ||
Latest Commit: | Version Fixed In: | 7.0.0 | |
Sentry Crash Report: | |||
Attachments: | backtrace of the crash |
Description
Hombre
2017-12-29 21:28:00 UTC
Sorry, forgot to mention: line 1273 of pentaxmn.cpp, but I guess you guessed it yourself :/ The crash appear in Exiv2 shared library. Please report this problem to Exiv2 project : http://www.exiv2.org/ Gilles Caulier The crash is reproducible with the exiv2 CLI tool. Maik Hombre, This file is definitively an UPSTREAM one. Please report this problem to Exiv2 bugzilla. Nothing can be changed in digiKam source code. Thanks in advance. Gilles Caulier Exiv2 now lives mainly on github and has two (?) new active devs. Please report any issues there (redmine/bugzilla on exiv2.org is still online, but not active): https://github.com/Exiv2/exiv2/issues I reproduced this on exiv2's master and took the liberty to already report it upstream: https://github.com/Exiv2/exiv2/issues/201 Thanks Simon for the upstream task Gilles Thanks for the prompt reply, and yeah, I should have figured out to report it on the right project... Sorry for the lost time on this. The issue has been fixed on January 13th in this commit https://github.com/Exiv2/exiv2/commit/b7d76da9d554a9dada7ca0a4e2d9cbc84c8b3847 However digiKam 5.9.0 still crash at the same location. I guess you still provide the unpatched exiv2 library. I managed to build the last version of exiv2 (Release and Debug build), however digiKam still crash but not at the same location. I guess problem can arise due to version mismatch between the old include file and the new library? Could you build and provide the last exiv2 library in your next Release please ? I just reopened the issue to put it on your radar, I'll let you close it again... The digiKam bundles (Linux, Windows, MacOS) use the official Exiv2 0.26 release which is the last one published. The fix for your problem come from Exiv2 implementation. It have been fixed in January 2018. Exiv2 0.26 have been release in May 2017. Do you feel the problem ? There is no maintenance release of Exiv2 since more than one year, and i refuse to use development code in a stable digiKam release. Exiv2 project must plan small release more frequently. This is the base of open source project management. So, no way. This file must be closed as UPSTREAM bug and the real problem reported to Exiv2 team... Gilles Caulier I just overlooked that there was so few release of exiv2. I'll just wait for the next DigiKam release then, which will include the last exiv2 library. Bonne journée Not reproducible with digiKam 7.0.0-beta1. |