dead letters crash

[Daniel Vrátil]

DrKonqi sometimes fails to catch the crash. You should be able to launch Kontact in gdb though and get the backtrace manually once it crashes. 


From the warnings it looks more like there's a problem with the Akonadi Server (that's the complaints about invalid socket name) not running. Still a bug, apps should not crash when Akonadi crashes. The dumped letters is what KMail automatically does on every crash to make sure you don't lose aby data in case it would crash while composing an email. 

RelWithDebInfo should be good enough. 

Dan


  Original Message  
From: winter at kde.org
Sent: May 15, 2017 00:14
To: kde-pim at kde.org
Reply-to: kde-pim at kde.org
Subject: Re: dead letters crash

On Sunday, May 14, 2017 6:09:05 PM EDT Allen Winter wrote:
> I've been using hand-built kde-pim master inside my KDE 16.08 desktop
> worked fine for a couple days.
> 
> But today I get this crash.  Looks familiar but I can't recall the trick to making it run again.
> any remember?  was it an autosave file I need to remove?
> the core file has no symbols for some reason.
> 
Hmm.. I build with CMAKE_BUILD_TYPE=RelWithDebInfo, as shown in
https://community.kde.org/KDE_PIM/Development/Start#Compiling

I wonder if I should be using debugfull instead?

> 
> org.kde.pim.akonadicore: "QLocalSocket::connectToServer: Invalid name" "/home/allen/.local-dev/share/akonadi/instance/devel/akonadiserver-cmd.socket"
> org.kde.pim.akonadicore: "QLocalSocket::connectToServer: Invalid name" "/home/allen/.local-dev/share/akonadi/instance/devel/akonadiserver-cmd.socket"
> org.kde.pim.webengineviewer:  It's not necessary to check database now
> *** KMail got signal 11 (Exiting)
> *** Dead letters dumped.
> KCrash: crashing... crashRecursionCounter = 2
> KCrash: Application Name = kontact path = /home/data/kde/inst/5/bin pid = 19140
> KCrash: Arguments: /home/data/kde/inst/5/bin/kontact 
> Segmentation fault (core dumped)
> 
>