https://bugs.kde.org/show_bug.cgi?id=426597
--- Comment #15 from caulier.gil...@gmail.com ---
Ha, this part of code is just imported from libraw project as well in digiKam
core. The trace is clear : this memory corruption is done when you extract a
preview image from Raw, not while Raw demosaicing.
For this kind of ASAN report, please :
1/ try to identify which Raw image introduce this memory leak,
2/ Use libraw CLi tool to extract preview image. No need to checkout libraw
code outside digiKam, we compile all libraw CLI tool in digiKam tests suite.
You will found all CLI tools in your build directory. Right tool is this one
with "-e" option :
[gilles@pc-gilles rawengine]$ pwd
/mnt/devel/GIT/7.x/build/core/tests/rawengine
[gilles@pc-gilles rawengine]$ ./simple_dcraw
simple_dcraw - LibRaw 0.20.0-Release sample. Emulates dcraw [-D] [-T] [-v] [-e]
[-E]
1134 cameras supported
Usage: ./simple_dcraw [-D] [-T] [-v] [-e] raw-files....
-4 - 16-bit mode
-L - list supported cameras and exit
-v - verbose output
-T - output TIFF files instead of .pgm/ppm
-e - extract thumbnails (same as dcraw -e in separate run)
[gilles@pc-gilles rawengine]$
3/ Look if ASAN dysfunction still exists
4/ Report this upstream problem to libraw team :
https://github.com/LibRaw/LibRaw/issues
Thanks in advance
Gilles Caulier
--
You are receiving this mail because:
You are watching all bug changes.
