Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 16 Jun 2004 01:37:46 -0400
From:      Joe Marcus Clarke <marcus@marcuscom.com>
To:        Sean McNeil <sean@mcneil.com>
Cc:        freebsd-gnome@freebsd.org
Subject:   Re: firefox core dump
Message-ID:  <1087364265.24564.8.camel@shumai.marcuscom.com>
In-Reply-To: <1087349838.99586.2.camel@server.mcneil.com>
References:  <1087349838.99586.2.camel@server.mcneil.com>

next in thread | previous in thread | raw e-mail | index | archive | help

--=-kCO7rFEToR0yqZWSrz8G
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

On Tue, 2004-06-15 at 21:37, Sean McNeil wrote:
> I just got done rebuilding firefox on amd64 and I get a sigbus on
> startup.  I had
>=20
> CFLAGS=3D -O -pipe -g
> STRIP=3D
>=20
> in my make.conf, but it didn't make a difference for the traceback:
>=20
> (gdb) bt
> #0  0x0000000200835a64 in non-virtual thunk to
> nsDirectoryService::AddRef() ()
>    from /usr/X11R6/lib/firefox/lib/firefox-0.9/libxpcom.so
> #1  0x00000002008350a3 in nsDirectoryService::~nsDirectoryService ()
>    from /usr/X11R6/lib/firefox/lib/firefox-0.9/libxpcom.so
> #2  0x0000000200834ddc in nsDirectoryService::Create ()
>    from /usr/X11R6/lib/firefox/lib/firefox-0.9/libxpcom.so
> #3  0x000000020081c4a2 in NS_InitXPCOM2 ()
>    from /usr/X11R6/lib/firefox/lib/firefox-0.9/libxpcom.so
> #4  0x0000000000407747 in ScopedXPCOMStartup::Initialize ()
> #5  0x00000000004089b2 in ScopedXPCOMStartup::SetWindowCreator ()
> #6  0x0000000000408e74 in ScopedXPCOMStartup::SetWindowCreator ()
> #7  0x00000000004098fa in xre_main ()
> #8  0x00000000004058a0 in main ()
>=20
> Is that DirectoryService as in ldap?

No, this is the component registration stuff.  However, this stack trace
doesn't make much sense.  I have a feeling there is some more amd64 work
that needs to be done for Mozilla 1.7-based browsers.  I was kind of
hoping the amd64 team could have a look since I'm shy on hardware, and
they have the requisite architecture knowledge.

Mezz's recommendation is the best course of action right now.  Try to
get a more coherent stack trace, and maybe this will turn out to be an
easy solution.

Joe

>=20
>=20
> _______________________________________________
> freebsd-gnome@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-gnome
> To unsubscribe, send any mail to "freebsd-gnome-unsubscribe@freebsd.org"
--=20
PGP Key : http://www.marcuscom.com/pgp.asc

--=-kCO7rFEToR0yqZWSrz8G
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (FreeBSD)

iD8DBQBAz9ypb2iPiv4Uz4cRAo+KAJ9z2w/1Z8Xv78LImxSILDJbGNOrvgCdEZBr
tGjQDzV6TmCl7Y9szMqcG4U=
=EV9y
-----END PGP SIGNATURE-----

--=-kCO7rFEToR0yqZWSrz8G--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1087364265.24564.8.camel>