Date: Mon, 3 Jun 2013 10:50:31 +0300 From: Konstantin Belousov <kostikbel@gmail.com> To: Dimitry Andric <dim@FreeBSD.org> Cc: Ted Faber <faber@lunabase.org>, freebsd-ports@freebsd.org Subject: Re: Another Firefox 21.0 crash (new backtrace) Message-ID: <20130603075031.GJ3047@kib.kiev.ua> In-Reply-To: <F1105EC2-17E7-44F8-9488-FBC02DCF1CA1@FreeBSD.org> References: <20130525230731.GA93415@mail.lunabase.org> <51A49C40.1080209@FreeBSD.org> <20130528155234.GA17344@mail.lunabase.org> <20130529035333.GA2340@mail.lunabase.org> <6B3D745E-9ADD-4B2A-B2C0-53B920B9CC71@FreeBSD.org> <20130602213125.GB87577@mail.lunabase.org> <F1105EC2-17E7-44F8-9488-FBC02DCF1CA1@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--4qnW9meeKZ7ZkKaT Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Jun 03, 2013 at 12:15:43AM +0200, Dimitry Andric wrote: > On Jun 2, 2013, at 23:31, Ted Faber <faber@lunabase.org> wrote: > > On Sun, Jun 02, 2013 at 05:35:27PM +0200, Dimitry Andric wrote: > >> As a better fix, please try dropping the attached file into the > >> /usr/ports/www/firefox/files directory, then rebuild the firefox port > >> from scratch, and reinstall it. > >=20 > > That works as well - firefox runs with compat6x installed, but compliled > > with the patch to www/firefox . > >=20 > > Thanks again for debugging this! >=20 >=20 > Well, the mystery is not entirely solved, as Firefox does not crash with > a similar failure on -current, even with the compat6x libc.so.6 > installed, and without the patch to osfile_unix_allthreads.jsm. >=20 > So *something* is different in the way multiple versions of libc.so are > handled, when they are loaded into the same process. Kostik, maybe you > have any idea? The same library of different version loaded into the process address space causes all sort of funny effects which are not very useful to investigate in the details. E.g., non-hidden private symbols both function and data types which are also present in the earlier library are resolved to the symbols from earlier library. The split definitely causes complicated and contradictory behaviour. In other words, if not loading libc.so.6 makes the process behave, I consider the case closed. --4qnW9meeKZ7ZkKaT Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.20 (FreeBSD) iQIcBAEBAgAGBQJRrErHAAoJEJDCuSvBvK1BbE4P/340tfwzOf2Eghk8VpmAWpbv ogeJfrYbxHaL61GbvriFpHayKBbLgh9McPS4M8DVSpXHtux4xvDH9rR7+yEBXlaT 02CPDqbWQ/cxhBYpyXtEmui3zrg+eaXdF2k5ayxdeGZN2b9IylYHZv/tT4zAmtrW pI2YvzaUbkYF1VZn1nYTwcXDvMcwlDALIpr9+SEx275F0JG8DlJLNNDdHyMoSZka xzBwKe2JsGIqlm+o4vPxhEZwPFr8CqJCjUStCxHR+RyNm837p2jg5gUjflPOxSyC F3W5vTY1gQcuuhOksBtan5XWLx3vNMwXTj+dAXZKHQht56FEGp4tvz2t3k2C9COT JSNxxF/43ZMRj4YKCpjwElZn6xgXhPriJUtq+46u1Xt+atGvXeATpKXyXLkeqtHK yXDmTG7f8nI3FnYKRUDM0kajrPXTnbGsmeOUeXm8vNu1NrCnLTH1Suhx2QSv1jiD dTtQ1itFVa5w4CSS7/tJnKKZBXKdD/bNgkAJHEdpmrXDdvUpsAwn2qjSJvGhpLSp 0bqMM0TvYNjL9lwMi1pIKKtjd+djnyCzkeGnhR5xV/ag/H/n0tbEbE2jJDB5vDbC qJmINjSlZ8WLWxMyOV2MsC83SRc6mYyj8QuzH44F0C+TAPSxZI6ZsPQTLPEgRYFu /x/02xGRfLzLljoSUdGR =ggN6 -----END PGP SIGNATURE----- --4qnW9meeKZ7ZkKaT--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20130603075031.GJ3047>