debugging akonadi_control

[Milian Wolff]

On Dienstag, 11. Dezember 2018 12:02:12 CET Jos van den Oever wrote:
> Hello all,
> 
> 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.
> 
> What would be better way of getting to the cause of the crashes?
> 
> Best regards,
> Jos
> 
> $ gdb -p 25515
> GNU gdb (GDB) 8.1.1
> Copyright (C) 2018 Free Software Foundation, Inc.
> License GPLv3+: GNU GPL version 3 or later
> <http://gnu.org/licenses/gpl.html> This is free software: you are free to
> change and redistribute it. There is NO WARRANTY, to the extent permitted
> by law.  Type "show copying" and "show warranty" for details.
> This GDB was configured as "x86_64-unknown-linux-gnu".
> Type "show configuration" for configuration details.
> For bug reporting instructions, please see:
> <http://www.gnu.org/software/gdb/bugs/>.
> Find the GDB manual and other documentation resources online at:
> <http://www.gnu.org/software/gdb/documentation/>.
> For help, type "help".
> Type "apropos word" to search for commands related to "word".
> Attaching to process 25515
> [New LWP 25516]
> [New LWP 25517]
> [Thread debugging using libthread_db enabled]
> Using host libthread_db library
> "/nix/store/fg4yq8i8wd08xg3fy58l6q73cjy8hjr2-
> glibc-2.27/lib/libthread_db.so.1".
> 0x00007f36ec710501 in poll ()
>    from /nix/store/fg4yq8i8wd08xg3fy58l6q73cjy8hjr2-glibc-2.27/lib/libc.so.6
> warning: File
> "/nix/store/zk5zj2307zxaq7dx585yia3dn5k4qlsl-gcc-7.3.0-lib/lib/
> libstdc++.so.6.0.24-gdb.py" auto-loading has been declined by your
> `auto-load safe-path' set to "$debugdir:$datadir/auto-load".
> To enable execution of this file add
>         add-auto-load-safe-path /nix/store/zk5zj2307zxaq7dx585yia3dn5k4qlsl-
> gcc-7.3.0-lib/lib/libstdc++.so.6.0.24-gdb.py
> line to your configuration file "/home/oever/.gdbinit".
> To completely disable this security protection add
>         set auto-load safe-path /
> line to your configuration file "/home/oever/.gdbinit".
> For more information about this security protection see the
> "Auto-loading safe path" section in the GDB manual.  E.g., run from the
> shell: info "(gdb)Auto-loading safe path"
> (gdb) cont
> Continuing.
> [Thread 0x7f36d9fc3700 (LWP 25516) exited]
> [Thread 0x7f36cc03d700 (LWP 25517) exited]
> [Inferior 1 (process 25515) exited with code 0377]
> (gdb) back
> No stack.

One cool new tool that you may not be familiar with yet is rr. You could just 
trace akonadi_control until it crashes/exits and then replay to see what 
happens, and why.

See: https://github.com/mozilla/rr

Cheers

-- 
Milian Wolff
mail at milianw.de
http://milianw.de
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-pim/attachments/20181211/d8ce87e8/attachment.sig>