https://bugs.kde.org/show_bug.cgi?id=433120

--- Comment #3 from Méven Car <meve...@gmail.com> ---
(In reply to Ray from comment #2)
> Removing the file does not seem to help. Rebooting starting with a new 
> blank account does not work.
> 
> Any other suggestions? Thanks.
> 

Not really, it seems the bug is in sqlite3 that crashes at an allocation stage.

#7  0x0000000806164094 in sqlite3DbMallocRawNN (db=0x4b, n=32) at
sqlite3.c:24518
#8  0x0000000806157c28 in sqlite3DbMallocRaw (db=0x4b, n=32) at sqlite3.c:24507
#9  0x000000080617f8da in sqlite3VdbeMemGrow (pMem=0x81f2883f8, n=32,
bPreserve=1) at sqlite3.c:68897
#10 0x0000000806154037 in sqlite3VdbeMemMakeWriteable (pMem=0x81f2883f8) at
sqlite3.c:68959
#11 0x000000080617fd98 in sqlite3VdbeMemTranslate (pMem=0x81f2883f8,
desiredEnc=2 '\002') at sqlite3.c:26970
#12 0x000000080617fbdf in sqlite3VdbeChangeEncoding (pMem=0x81f2883f8,
desiredEnc=2) at sqlite3.c:68861
#13 0x000000080617faec in valueToText (pVal=0x81f2883f8, enc=2 '\002') at
sqlite3.c:69784
#14 0x0000000806153dd5 in sqlite3ValueText (pVal=0x81f2883f8, enc=2 '\002') at
sqlite3.c:69827
#15 0x0000000806153e0a in sqlite3_value_text16 (pVal=0x81f2883f8) at
sqlite3.c:75323
#16 0x000000081f31f367 in columnName (pStmt=0x819e11d08, N=3, useUtf16=1,
useType=3) at sqlite3.c:84452

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to