Date: Thu, 28 Jul 2016 15:37:00 -0400 From: Jung-uk Kim <jkim@FreeBSD.org> To: freebsd-hackers@freebsd.org Subject: Re: Segfault in OpenSSL even though GnuTLS demanded Message-ID: <599ca93e-31ed-fcb4-75de-7d05667d928e@FreeBSD.org> In-Reply-To: <20160728180255.GA79509@becker.bs.l> References: <20160728180255.GA79509@becker.bs.l>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --6VCvBQXHI5bdPoRIVrvKSB26ONCN5nL7n Content-Type: multipart/mixed; boundary="Vf8nTahAUtuJWK5sgd02NPTxmWHqioLGI" From: Jung-uk Kim <jkim@FreeBSD.org> To: freebsd-hackers@freebsd.org Message-ID: <599ca93e-31ed-fcb4-75de-7d05667d928e@FreeBSD.org> Subject: Re: Segfault in OpenSSL even though GnuTLS demanded References: <20160728180255.GA79509@becker.bs.l> In-Reply-To: <20160728180255.GA79509@becker.bs.l> --Vf8nTahAUtuJWK5sgd02NPTxmWHqioLGI Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On 07/28/16 02:02 PM, Bertram Scharpf wrote: > Hi, >=20 > first of all, I am compiling ports myself. No packages. >=20 > I try to install a console XMPP client. To my > disappointment, both irssi-xmpp and mcabber, too, crash with > the same segfault. Here's an output from gdb. >=20 > Program received signal SIGSEGV, Segmentation fault. > [Switching to Thread 29403080 (LWP 101275/mcabber)] > 0x285c1245 in OPENSSL_ia32_cpuid () from /usr/local/lib/libcrypto.so.= 8 >=20 > Both ports do no SSL themselves but depend on loudmouth. > However, I have disabled OpenSSL there. >=20 > # grep SSL\\\|TLS /var/db/ports/net-im_loudmouth/options > _FILE_COMPLETE_OPTIONS_LIST=3DDOCS GNUTLS OPENSSL > OPTIONS_FILE_SET+=3DGNUTLS > OPTIONS_FILE_UNSET+=3DOPENSSL >=20 > I have checked the ./configure calls parameters and there is a > --with-ssl=3Dgnutls indeed. >=20 > I tried to config loudmouth with OpenSSL instead of GnuTLS, > but I encounter the same segfault. >=20 > What is going on here? What can I do further? Try "ldd /usr/local/lib/libloudmouth-1.so.0.1.0". It looks like a Kerberos issue. Jung-uk Kim --Vf8nTahAUtuJWK5sgd02NPTxmWHqioLGI-- --6VCvBQXHI5bdPoRIVrvKSB26ONCN5nL7n Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJXml7iAAoJEHyflib82/FGOvIH/2RmHrwUbMyHOkQ25R9y8vsT QC1bSaAG8lm1ylC/Y49evIuQ3AZRx3gSeZ8KrVtZAFbBkVMy++QRW8ySecPsN6/K 106O9USWAiBtwMBe0xFWiLrkLOoCLR36z2TgDW7MiVGbx/HX+ELXboUubMMMC1nj wRwv50CmsOPkZN52TfNnif1qZabOReTOszCvQKzREufmlbXe3wRuf/rh9+LljSC/ cwd5U5+ROClav2dZr/gu5EfVY1SSQlnhUcDMBBH7r3HqqyNo9i6emSIb9GDpB8zc 8CKjg67YuNfLvE9PtXvzC1HUo86/yGKlpXX/LTy7iVMjApbkDx2YZJQZg09oqeQ= =Ck4+ -----END PGP SIGNATURE----- --6VCvBQXHI5bdPoRIVrvKSB26ONCN5nL7n--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?599ca93e-31ed-fcb4-75de-7d05667d928e>