I can confirm experiences of Andreas Mair in comment #13:
I also use Gentoo Linux. Since a few weeks, digikam crashes at all kinds of actions: Editing photos, assigning tags, ...
KDE crash handler always lists sqlite:
Thread 1 (Thread 0x7f6245ec5800 (LWP 1870)):
[KCrash Handler]
#6 0x00000000036ed770 in ?? ()
#7 0x00007f62310d0dae in sqlite3MemCompare (pMem1=<optimized out>, pMem2=0x3ea0728, pColl=0x4a647b8) at sqlite3.c:60468
#8 0x00007f62310d10dd in sqlite3VdbeRecordCompare (nKey1=18, pKey1=0x7f62242528e9, pPKey2=0x7ffff2e9cbe0) at sqlite3.c:64160
#9 0x00007f62310f277b in sqlite3BtreeMovetoUnpacked (pRes=<optimized out>, biasRight=<optimized out>, intKey=<optimized out>, pIdxKey=<optimized out>, pCur=<optimized out>) at sqlite3.c:55075
#10 sqlite3BtreeMovetoUnpacked (pCur=0x42fc920, pIdxKey=0x7ffff2e9cbe0, intKey=0, biasRight=<optimized out>, pRes=0x7ffff2e9cbd0) at sqlite3.c:54960
#11 0x00007f62310fde0e in sqlite3VdbeExec (p=0xaf72d78) at sqlite3.c:70166
#12 0x00007f623110645f in sqlite3Step (p=0xaf72d78) at sqlite3.c:64826
...
Looking at my emerge.log, I did an update of "dev-db/sqlite-3.7.17" to "dev-db/sqlite-3.8.2" 8 weeks ago.
> After downgrading sqlite 3.8.2 to 3.7.17 everything is fine again. No more crashes!
Thanks for the tip! By today, there is no more "sqlite-3.7.x" in portage tree. So I will try the current top up-to-date version "dev-db/sqlite-3.8.4.3".
I can confirm experiences of Andreas Mair in comment #13:
I also use Gentoo Linux. Since a few weeks, digikam crashes at all kinds of actions: Editing photos, assigning tags, ...
KDE crash handler always lists sqlite: rdCompare (nKey1=18, pKey1=0x7f62242 528e9, pPKey2= 0x7ffff2e9cbe0) at sqlite3.c:64160 etoUnpacked (pRes=<optimized out>, biasRight= <optimized out>, intKey=<optimized out>, pIdxKey=<optimized out>, pCur=<optimized out>) at sqlite3.c:55075 etoUnpacked (pCur=0x42fc920, pIdxKey= 0x7ffff2e9cbe0, intKey=0, biasRight= <optimized out>, pRes=0x7ffff2e9 cbd0) at sqlite3.c:54960
Thread 1 (Thread 0x7f6245ec5800 (LWP 1870)):
[KCrash Handler]
#6 0x00000000036ed770 in ?? ()
#7 0x00007f62310d0dae in sqlite3MemCompare (pMem1=<optimized out>, pMem2=0x3ea0728, pColl=0x4a647b8) at sqlite3.c:60468
#8 0x00007f62310d10dd in sqlite3VdbeReco
#9 0x00007f62310f277b in sqlite3BtreeMov
#10 sqlite3BtreeMov
#11 0x00007f62310fde0e in sqlite3VdbeExec (p=0xaf72d78) at sqlite3.c:70166
#12 0x00007f623110645f in sqlite3Step (p=0xaf72d78) at sqlite3.c:64826
...
Looking at my emerge.log, I did an update of "dev-db/ sqlite- 3.7.17" to "dev-db/ sqlite- 3.8.2" 8 weeks ago.
> After downgrading sqlite 3.8.2 to 3.7.17 everything is fine again. No more crashes! sqlite- 3.8.4.3" .
Thanks for the tip! By today, there is no more "sqlite-3.7.x" in portage tree. So I will try the current top up-to-date version "dev-db/