https://bugs.kde.org/show_bug.cgi?id=377656
Rex Dieter changed:
What|Removed |Added
CC||rdie...@math.unl.edu
--
You are receiving this ma
https://bugs.kde.org/show_bug.cgi?id=377656
--- Comment #6 from Steve ---
Some information printed to the console around the time of another abort:
org.kde.pim.akonadicore: Got a stale notification for an item which was already
removed. 2061954 ""
org.kde.pim.akonadicore: Got a stale notificatio
https://bugs.kde.org/show_bug.cgi?id=377656
Daniel Vrátil changed:
What|Removed |Added
Ever confirmed|0 |1
Status|UNCONFIRMED
https://bugs.kde.org/show_bug.cgi?id=377656
Daniel Vrátil changed:
What|Removed |Added
CC||m...@vowleyfarm.co.uk
--- Comment #5 from Danie
https://bugs.kde.org/show_bug.cgi?id=377656
--- Comment #4 from Steve ---
In src/server/connection.cpp at line 404, there should probably be a try/catch
around the Protocol::serialize() call:
void Connection::sendResponse(qint64 tag, const Protocol::Command &response)
{
if (Tracer::self()->c
https://bugs.kde.org/show_bug.cgi?id=377656
--- Comment #3 from Dennis Schridde ---
DrKonqi suggested both bugs, this and duplicates of the other, as possible
duplicates of a crash that I was experiencing. I assumed that was because the
backtrace was the same.
--
You are receiving this mail bec
https://bugs.kde.org/show_bug.cgi?id=377656
--- Comment #2 from Steve ---
I think this is different because its dying via an abort() call. They are
usually placed in code to stop a program when its doing something that violates
some expectation. The idea is to force a coredump to collect a backtr
https://bugs.kde.org/show_bug.cgi?id=377656
Dennis Schridde changed:
What|Removed |Added
CC||dennis.schridde@uni-heidelb
