On Fri, May 10, 2013 at 4:31 AM, Erwin Geerdink <[email protected]> wrote: > I have little experience with debugging. I got the following output > from gdb, not sure if it's useful. Please let me know if you need > additional information.
It's a reasonable start. :-) > (gdb) r > Starting program: /usr/local/bin/claws-mail > ** (claws-mail:548): WARNING **: plugin loading error: File not found > [New process 548] > ** (claws-mail:548): WARNING **: couldn't gnutls_x509_crt_export to get size > ** (claws-mail:548): WARNING **: couldn't gnutls_x509_crt_export to get size > ** (claws-mail:548): WARNING **: couldn't gnutls_x509_crt_export to get size > a The request is invalid. > > Program received signal SIGSEGV, Segmentation fault. > 0x00001e8d3180bed6 in _gnutls_x509_crt_get_raw_dn2 () > from /usr/local/lib/libgnutls.so.39.2 > (gdb) bt > #0 0x00001e8d3180bed6 in _gnutls_x509_crt_get_raw_dn2 () > from /usr/local/lib/libgnutls.so.39.2 So, looks like it tried to do something (gnutls_x509_crt_export) with a/some certificate(s), which failed, and then it made another call (ssl_certificate_check_signer) which blew up. My first guess is that the earlier failures led to an empty certificate store in memory which blew up the later check and (still guessing) that this was caused by a change in the format accepted by gnutls, such that your existing certificate(s) are no longer acceptable. I therefore suggest verifying the contents/format of your certificate and/or CAs against the gnutls tools, reloading them from PEM or whatever. That the best I can suggest, as I don't use gnutls for anything myself. The quality of the error checking demonstrated by this crash, btw, should have you filing bugs with the claws-mail developers. "Bad input files" is not a valid reason to crash; it should be reporting what file is involved and the most precise error message it has for the problem and existing with a non-zero status. Philip Guenther
