Bug#944915: libldap-2.4-2: Segmentation fault in "ldap_unbind_ext"
devel at sumpfralle.de
devel at sumpfralle.de
Tue Nov 19 22:31:19 GMT 2019
Hello Bernhard,
Am Tue, 19 Nov 2019 11:55:54 +0100
schrieb Bernhard Übelacker <bernhardu at mailbox.org>:
> 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?
An interesting idea!
I could imagine, that claws-mail's maintainer will appreciate this hint.
(I guess, I will open a bug report against claws-mail upstream)
> In that case following gdb output would show all
> threads with their backtraces:
> (gdb) thread apply all bt
indeed this was the command, that I used to generate the gdb output.
> Or with showing also the variables:
> (gdb) thread apply all bt full
Next time I will also use this one.
> And how do you get the backtraces? Are you running
> with a gdb attached to it permanently?
Yes, I am doing this for claws-mail at the moment.
> Then you could create a core when the crash happened with
> (gdb) generate-core-file /home/someone/corefile
Good point - I will try this next time.
Thank you for your hints!
Cheers,
Lars
More information about the Pkg-openldap-devel
mailing list