https://bugs.kde.org/show_bug.cgi?id=425723
Simon Westersund <simon.westers...@iki.fi> changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #131132|0 |1
is obsolete| |
--- Comment #3 from Simon Westersund <simon.westers...@iki.fi> ---
Created attachment 131155
--> https://bugs.kde.org/attachment.cgi?id=131155&action=edit
gdb backtrace with digikam built from source
I decided to try and compile digikam from source to provide the best possible
backtrace.
So I built digikam from the GitLab sources' master branch (commit
fa696a690fccf81a3b1ff70f1271e1cb0b19339e) with the bootstrap.local script. I
made the following changes to the bootstrap.linux options, to avoid a build
problem with a test, which I encountered:
-DBUILD_TESTING=OFF
-DENABLE_MYSQLSUPPORT=OFF
-DENABLE_INTERNALMYSQL=OFF
If you need any extra info, please let me know :)
The backtrace is from a crash where I used the "Scan again and merge results"
and "Work on all processor cores" options on the same collection that I scanned
previously. The crash appeared at 6% completion.
--
You are receiving this mail because:
You are watching all bug changes.
