Date: Sun, 20 May 2007 13:26:12 +0300 From: "Vlad GALU" <dudu@dudu.ro> To: freebsd-current@freebsd.org Subject: Re: HEADS UP: OpenSSL problems after GCC 4.2 upgrade Message-ID: <ad79ad6b0705200326o5e16c12ode66966c6c53b4b0@mail.gmail.com> In-Reply-To: <20070520102018.GA41098@tirith.brixandersen.dk> References: <20070520022722.1f5a0cda@kan.dnsalias.net> <20070520082913.GX23313@hoeg.nl> <20070520102018.GA41098@tirith.brixandersen.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
On 5/20/07, Henrik Brix Andersen <henrik@brixandersen.dk> wrote: > On Sun, May 20, 2007 at 10:29:13AM +0200, Ed Schouten wrote: > > Hello Alexander, > > > > * Alexander Kabaev <kabaev@gmail.com> wrote: > > > there were several reports of OpenSSL being broken when compiled with > > > GCC 4.2. It turns out OpenSSL uses function casting feature that was > > > aggressively de-supported by GCC 4.2 and GCC goes as far as inserting > > > invalid instructions ON PURPOSE to discourage the practice. > > > > Is that the reason why portsnap returns SIGILL's on my box after the > > upgrade? > > Most likely, yes. Check /var/log/messages. There might be a PEBKAC here, but after applying the patch (cleanly) and rebuilding/reinstalling everything under /usr/src/secure, OpenVPN still crashes with SIGILL. > > Regards, > Brix > -- > Henrik Brix Andersen <henrik@brixandersen.dk> > > -- If it's there, and you can see it, it's real. If it's not there, and you can see it, it's virtual. If it's there, and you can't see it, it's transparent. If it's not there, and you can't see it, you erased it.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ad79ad6b0705200326o5e16c12ode66966c6c53b4b0>