debugging akonadi_control

Tue Dec 11 12:55:02 GMT 2018

Unfortunately, while debugging with gdb on akonadi_control, I've managed 
to get kmail into a state where it will crash on startup.
Starting kmail briefly shows kmail and then crashes with this backtrace:

$ kmail
Received signal 11 SEGV_MAPERR 0000bbadbeef
#0 0x7f0d57a8119e <unknown>
#1 0x7f0d5640807c <unknown>
#2 0x7f0d57a81687 <unknown>
#3 0x7f0d648f6c50 <unknown>
#4 0x7f0d4641d950 <unknown>
#5 0x7f0d464a8d83 <unknown>
#6 0x7f0d464a91d8 <unknown>
#7 0x7f0d4654f0e5 <unknown>
#8 0x7f0d4654fc4f QScriptEngine::QScriptEngine()
#9 0x7f0d544495b2 Grantlee::ScriptableTagLibrary::ScriptableTagLibrary()
#10 0x7f0d5441d093 Grantlee::Engine::loadDefaultLibraries()
#11 0x7f0d5443104b Grantlee::Parser::Parser()
#12 0x7f0d5443c5a8 Grantlee::TemplatePrivate::compileString()
#13 0x7f0d5443c827 Grantlee::TemplateImpl::setContent()
#14 0x7f0d54419a80 Grantlee::Engine::newTemplate()
#15 0x7f0d4c9b9c41 GrantleeTheme::QtResourceTemplateLoader::loadByName()
#16 0x7f0d5441a239 Grantlee::Engine::loadByName()
#17 0x7f0d62663e70 
MessageViewer::MessagePartRendererManager::loadByName()
#18 0x7f0d62667580 MessageViewer::TextMessagePartRenderer::render()
#19 0x7f0d6265a2db 
MessageViewer::DefaultRendererPrivate::renderWithFactory()
#20 0x7f0d6265eec2 
MessageViewer::DefaultRendererPrivate::renderFactory()
#21 0x7f0d6265fd0b 
MessageViewer::DefaultRendererPrivate::renderSubParts()
#22 0x7f0d62659512 MessageViewer::DefaultRendererPrivate::render()
#23 0x7f0d62659783 MessageViewer::DefaultRendererPrivate::render()
#24 0x7f0d6265f78b 
MessageViewer::DefaultRendererPrivate::renderFactory()
#25 0x7f0d6265fd0b 
MessageViewer::DefaultRendererPrivate::renderSubParts()
#26 0x7f0d626592a6 MessageViewer::DefaultRendererPrivate::render()
#27 0x7f0d6265efb0 
MessageViewer::DefaultRendererPrivate::renderFactory()
#28 0x7f0d626600d4 MessageViewer::DefaultRenderer::render()
#29 0x7f0d626822c2 MessageViewer::EmptySource::render()
#30 0x7f0d5ff08467 MimeTreeParser::ObjectTreeParser::parseObjectTree()
#31 0x7f0d62693997 MessageViewer::ViewerPrivate::parseContent()
#32 0x7f0d62693ec5 MessageViewer::ViewerPrivate::displayMessage()
#33 0x7f0d6269483b MessageViewer::ViewerPrivate::updateReaderWin()
#34 0x7f0d6586695f QMetaObject::activate()
#35 0x7f0d65873547 QTimer::timeout()
#36 0x7f0d658738a8 QTimer::timerEvent()
#37 0x7f0d6586732b QObject::event()
#38 0x7f0d665d402c QApplicationPrivate::notify_helper()
#39 0x7f0d665db5df QApplication::notify()
#40 0x7f0d65837608 QCoreApplication::notifyInternal2()
#41 0x7f0d65890bce QTimerInfoList::activateTimers()
#42 0x7f0d65891391 <unknown>
#43 0x7f0d4ef6df47 g_main_context_dispatch
#44 0x7f0d4ef6e180 g_main_context_iterate.isra.26
#45 0x7f0d4ef6e20c g_main_context_iteration
#46 0x7f0d6589173f QEventDispatcherGlib::processEvents()
#47 0x7f0d39fa4461 <unknown>
#48 0x7f0d6583593a QEventLoop::exec()
#49 0x7f0d6583ee00 QCoreApplication::exec()
#50 0x0000004041d5 main
#51 0x7f0d648e3b8e __libc_start_main
#52 0x00000040430a _start
   r8: 00000000ffffffff  r9: 0000000000000000 r10: 0000000000004022 r11: 
0000000000000246
  r12: 00007f0cec033800 r13: 00007f0cec03a960 r14: 0000000000004000 r15: 
0000000000004000
   di: 0000000000000000  si: 0000000080000000  bp: 0000000000004000  bx: 
00000000065ba6a0
   dx: ffffffffffffff40  ax: 00000000bbadbeef  cx: 00007f0d649af3d3  sp: 
00007ffcd8783460
   ip: 00007f0d4641d950 efl: 0000000000010246 cgf: 002b000000000033 erf: 
0000000000000006
  trp: 000000000000000e msk: 0000000000000000 cr2: 00000000bbadbeef
[end of stack trace]
Calling _exit(1). Core file will not be generated.

(this mail was sent from webmail)

On 11.12.2018 13:32, Jos van den Oever wrote:
> On Tuesday, 11 December 2018 12:07:22 CET you wrote:
>> > I've been experiencing daily crashes of akonadi_control. I'd like to
>> > figure
>> > out what's going on. I've attached gdb to get stack traces. Unfortunately,
>> > as you can see from the log below, akonadi_control crashes without giving
>> > an opportunity to show the backtraces.
>> 
>> Maybe it's not a crash but an exit, then?
> 
> That's true. It's an unexpected exit. KMail is running and somehow
> akondi_control decides to stop. Sometimes it restarts, sometimes it 
> doesn't
> and shows the 'Start' button in KMail.
> 
>> > What would be better way of getting to the cause of the crashes?
>> 
>> Try setting a breakpoint to _exit() to see where the program is 
>> terminated
>> from.
> 
> I've that running than and will see where it's called from. It will 
> probably
> work because it also stopped at _exit when calling `akonadictl 
> restart`.
> 
>> Also, when you run Akonadi from terminal (akonadictl restart), you 
>> should
>> see debug output of all Akonadi components, including akonadi_control 
>> -
>> maybe there could be some hint as to what's happening there?
> 
> There is a message about akonadi_maildir_resource_0.
> 
> ===
> $ org.kde.pim.akonadiserver: mysqld for Akonadi is already running, 
> trying to
> connect to it.
> akonadi.collectionattributetable                   OK
> akonadi.collectionmimetyperelation                 OK
> akonadi.collectionpimitemrelation                  OK
> akonadi.collectiontable                            OK
> akonadi.flagtable                                  OK
> akonadi.mimetypetable                              OK
> akonadi.parttable                                  OK
> akonadi.parttypetable                              OK
> akonadi.pimitemflagrelation                        OK
> akonadi.pimitemtable                               OK
> akonadi.pimitemtagrelation                         OK
> akonadi.relationtable                              OK
> akonadi.relationtypetable                          OK
> akonadi.resourcetable                              OK
> akonadi.schemaversiontable                         OK
> akonadi.tagattributetable                          OK
> akonadi.tagremoteidresourcerelationtable           OK
> akonadi.tagtable                                   OK
> akonadi.tagtypetable                               OK
> Connecting to deprecated signal
> QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
> org.kde.pim.akonadiserver: "Cannot connect to agent instance with 
> identifier
> 'akonadi_maildir_resource_0', error message: ''"
> ===
> 
> There is a process running that corresponds to resource_0:
>     akonadi_maildir_resource --identifier akonadi_maildir_resource_0
> 
> Some more information that might be pertinent. The version is 5.9.0 
> from KDE
> applications 18.08.0 running on NixOS 18.09.
> 
> When akonadi_control restarts, the current message list in KMail 
> becomes
> empty. When clicking on another folder and back to the previous folder, 
> the
> message list is visible again.
> 
> Cheers,
> Jos