https://bugs.kde.org/show_bug.cgi?id=443685
--- Comment #3 from John Beatty <hjohnbea...@gmail.com> --- Hi Gilles, Thanks for looking into this. I'm trying to put together the requested information. 1 These were raws from the Canon R5. 2 Exiv 11.88 3 I'm not sure how to get a GDB backtrace of the crash 4) I've attached two consoles one where it was not running in parallel and worked. I stopped it after about 150 or so files converted. So it works in serial mode. I've also attached a console with it running under catchsegv in parallel and failing. It doesn't appear to get to far. On this run it only completed 1 dng. The file with the failure has segfault in the name (digikam.segfault.console). Just for a bit more context I ran digikam in parallel without catchsegv and the messages from digikam appear to be virtually identical so I don't think the catchsegv alters the output other than to display the backtrace info at the end of the console. Thanks again for being so prompt in looking into this problem, John B. On 10/13/21 11:44 PM, bugzilla_nore...@kde.org wrote: > https://bugs.kde.org/show_bug.cgi?id=443685 > > --- Comment #1 from caulier.gil...@gmail.com --- > I cannot reproduce the crash here with my CR3 test files. > > Can you precise : > > - which Canon camera you use. > - Which Exiv2 version you use (Look in Help/Components Info for details). > - capture a GDB backtrace of crash. > - capture console traces during dysfunction. > > See instructions here: https://www.digikam.org/contribute/ > > Gilles Caulier > -- You are receiving this mail because: You are watching all bug changes.