Date: Mon, 1 Aug 2016 12:13:00 +0200 From: Bertram Scharpf <lists@bertram-scharpf.de> To: freebsd-hackers@freebsd.org Subject: Re: Segfault in OpenSSL even though GnuTLS demanded Message-ID: <20160801101300.GA48521@becker.bs.l> In-Reply-To: <CA%2B7WWScxvZ-2L-Wf0QXSFb9qTr0sUAx6-oncBhjqrgaLxB-zWw@mail.gmail.com> References: <20160728180255.GA79509@becker.bs.l> <599ca93e-31ed-fcb4-75de-7d05667d928e@FreeBSD.org> <20160728205516.GA94239@becker.bs.l> <b88fc3be-c10a-70b1-c985-f560ad86ecc0@FreeBSD.org> <20160728213717.GA98586@becker.bs.l> <7483738d-01e7-0bb2-81e9-9c26d8ef8c9f@FreeBSD.org> <20160729100952.GA4967@becker.bs.l> <CA%2B7WWScxvZ-2L-Wf0QXSFb9qTr0sUAx6-oncBhjqrgaLxB-zWw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Friday, 29. Jul 2016, 20:00:54 +0300, Kimmo Paasiala wrote: > >> >>>> On 07/28/16 02:02 PM, Bertram Scharpf wrote: > >> >>>>> > >> >>>>> 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 > >> >>>> > > It's not exactly a port bug, it's a consequence of how dynamic linking > works. As long as an installation with any configuration yields an unconditional segmentation fault on startup, it _is_ a port bug. However, I have several bug reports and fixes running anunswered for months. I do not expect anything edifying to happen if I submit another problem report. Bertram -- Bertram Scharpf Stuttgart, Deutschland/Germany http://www.bertram-scharpf.de
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20160801101300.GA48521>