Hello Lars, just a wild guess - is claws-mail doing these ldap queries in parallel in different threads? This in combination with the unsteady connection to the server could make two threads operate on the same structures?
In that case following gdb output would show all threads with their backtraces: (gdb) thread apply all bt Or with showing also the variables: (gdb) thread apply all bt full And how do you get the backtraces? Are you running with a gdb attached to it permanently? Then you could create a core when the crash happened with (gdb) generate-core-file /home/someone/corefile Otherwise you could have a look at a coredump collector like systemd-coredump and its setting Storage=external. With these files someone could examine them later for some more details, if the matching package and dbgsyms are installed. Kind regards, Bernhard