Date: Mon, 21 Jan 2008 23:58:39 -0500 From: Joe Marcus Clarke <marcus@marcuscom.com> To: Marius Strobl <marius@alchemy.franken.de> Cc: gnome@freebsd.org, freebsd-sparc64@freebsd.org, Stephen Hurd <shurd@sasktel.net> Subject: Re: Seamonkey core dumps at start in nsACString_internal::~nsACString_internal Message-ID: <1200977919.15266.22.camel@shumai.marcuscom.com> In-Reply-To: <20080121220950.GA38360@alchemy.franken.de> References: <477AC2A4.8080708@sasktel.net> <20080117213604.GA91984@alchemy.franken.de> <1200698886.67472.85.camel@shumai.marcuscom.com> <20080121220950.GA38360@alchemy.franken.de>
next in thread | previous in thread | raw e-mail | index | archive | help
--=-c/LptGtSE8FVr+2BEXT+ Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Mon, 2008-01-21 at 23:09 +0100, Marius Strobl wrote: > On Fri, Jan 18, 2008 at 06:28:06PM -0500, Joe Marcus Clarke wrote: > >=20 > > On Thu, 2008-01-17 at 22:36 +0100, Marius Strobl wrote: > > > On Tue, Jan 01, 2008 at 02:45:56PM -0800, Stephen Hurd wrote: > > > > The current Seamonkey port is core dumping for me in=20 > > > > nsACString_internal::~nsACString_internal > > > >=20 > > > > My options were: > > > > # This file is auto-generated by 'make config'. > > > > # No user-servicable parts inside! > > > > # Options for seamonkey-1.1.7 > > > > _OPTIONS_READ=3Dseamonkey-1.1.7 > > > > WITH_MAILNEWS=3Dtrue > > > > WITH_COMPOSER=3Dtrue > > > > WITHOUT_LDAP=3Dtrue > > > > WITH_CHATZILLA=3Dtrue > > > > WITH_JAVASCRIPT_DEBUGGER=3Dtrue > > > > WITHOUT_SMB=3Dtrue > > > > WITHOUT_DEBUG=3Dtrue > > > > WITHOUT_LOGGING=3Dtrue > > > > WITH_OPTIMIZED_CFLAGS=3Dtrue > > > >=20 > > > > Anyone have a set of options that does work? I expect that=20 > > > > WITHOUT_DEBUG and WITH_OPTIMIZED_CFLAGS at the very least should be= frobbed. > > >=20 > > > This seems to be due to a miscompilation or mislinkage problem > > > causing two nsObsoleteAString::sCanonicalVTable and two > > > nsObsoleteACString::sCanonicalVTable symbols shadowing each-other > > > respectively. To me this smells a a least bit like "you get what > > > you asked for" though; I'm surprised their string code actually > > > works somewhere. See the attachement for a patch that works around > > > the problem by omitting the code in question. > > > Dear gnome@ maintainers, could you please commit the attached > > > patch and bump the PORTREVISIONs of the affected ports (the > > > problem also affects at least www/firefox) or approve committing > > > such a change? > >=20 > > Approved! >=20 > Thanks! >=20 > > Does this also apply to other Gecko ports, or just seamonkey? >=20 > It's known to affect at least firefox and seamonkey, though the > other xpcom consumers are also most likely affected. I think this patch should take care of all of them then. Thanks. Joe >=20 > Marius >=20 >=20 --=20 PGP Key : http://www.marcuscom.com/pgp.asc --=-c/LptGtSE8FVr+2BEXT+ Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (FreeBSD) iEYEABECAAYFAkeVd/wACgkQb2iPiv4Uz4fKbQCfbY7nNi8DSuuZb26i9n/mWgzB VNQAn0Bmhstd2Yrji98ByEPoDsbIk6uw =7FQG -----END PGP SIGNATURE----- --=-c/LptGtSE8FVr+2BEXT+--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1200977919.15266.22.camel>