Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 30 Apr 2013 17:25:22 +0200
From:      Dimitry Andric <dim@freebsd.org>
To:        Brandon Gooch <jamesbrandongooch@gmail.com>
Cc:        kit <ktsin@acm.org>, freebsd-ports@freebsd.org
Subject:   Re: firefox build broken under clang 3.3
Message-ID:  <230B0687-FD64-4BC0-8EB6-D3D6ACD9CC3F@freebsd.org>
In-Reply-To: <CALBk6yLOV8fzdAY9y0_7SZvR9N8J-19FrwZjFv4t14ub8wmGiA@mail.gmail.com>
References:  <20130419020021.GA16918@test.yahoo.com> <51716917.90101@smeets.im> <F82EAEBA-C47D-4AC6-8FAE-AC3541B131C7@FreeBSD.org> <517187B9.40106@smeets.im> <CALBk6yLOV8fzdAY9y0_7SZvR9N8J-19FrwZjFv4t14ub8wmGiA@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Apr 30, 2013, at 05:28, Brandon Gooch <jamesbrandongooch@gmail.com> =
wrote:
...
> Thanks for fixing the build issues.
>=20
> Now, I've built Firefox with Clang, but the darn thing segfaults at
> the drop of a hat:
>=20
> $ gdb /usr/local/bin/firefox firefox.core
> ...
> (gdb) bt
> #0  0x00000008011eefaa in thr_kill () from /lib/libc.so.7
> #1  0x00000008024d254d in XRE_InstallX11ErrorHandler ()
>   from /usr/local/lib/firefox/libxul.so
> #2  0x0000000800f74116 in swapcontext () from /lib/libthr.so.3
> #3  0x0000000800f73d39 in sigaction () from /lib/libthr.so.3
> #4  0x00007ffffffff193 in ?? ()
> #5  0x0000000800f73c20 in sigaction () from /lib/libthr.so.3
> Previous frame inner to this frame (corrupt stack?)
>=20
> Rebuilding with debugging symbols provides no further insight, as that
> seems to provide a work-around for whatever the root cause may be
> (i.e. no more segfaults).
>=20
> Are any of you seeing something similar?

Which exact version of head do you have, and which version(s) of ports?  =
Are you running WITH_NEW_XORG or not?

In any case, I have just built the latest Firefox from ports, with clang =
3.3, and I see no issues at all.  At least with approximately 10 minutes =
of browsing, and visiting a varied bunch of sites.  I do have it built =
with debug info, but without cranking down the optimization level to -O0 =
(which is what bsd.port.mk seems to do, unfortunately).

I will rebuild it again, without any debug info, to see if that makes =
any difference.  I don't think it will, though...




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?230B0687-FD64-4BC0-8EB6-D3D6ACD9CC3F>