Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 11 May 2002 04:33:06 -0700
From:      Sean Chittenden <sean@chittenden.org>
To:        Joe Marcus Clarke <marcus@marcuscom.com>
Cc:        Chip Wiegand <chip@wiegand.org>, ports@FreeBSD.ORG
Subject:   Re: FreeBSD Port Mozilla - fails badly when I ran portupgrade
Message-ID:  <20020511043306.B29841@ninja1.internal>
In-Reply-To: <1019969494.742.6.camel@gyros.marcuscom.com>; from "marcus@marcuscom.com" on Sun, Apr 28, 2002 at = 12:51:34AM
References:  <20020423231838.60e8f150.chip@wiegand.org> <20020423232253.D61911@ninja1.internal> <1019675885.8815.46.camel@gyros.marcuscom.com> <20020424145609.O61911@ninja1.internal> <1019703039.297.12.camel@gyros.marcuscom.com> <20020424201320.A82196@ninja1.internal> <1019706431.26338.11.camel@gyros.marcuscom.com> <20020426233153.A51215@ninja1.internal> <1019969494.742.6.camel@gyros.marcuscom.com>

next in thread | previous in thread | raw e-mail | index | archive | help
> > > Can you try running mozilla from a directory you have write
> > > permissions on?  Of course, without debugging symbols, the core
> > > analysis might not do any good.
> > 
> > Not an issue...
> > 
> > > > Other ideas on how to get it to leave a trace?  -sc
> > > 
> > > Another option is to tie gdb to the running mozilla process:
> > > 
> > > gdb /usr/X11R6/lib/mozilla/mozilla-bin <PID of mozilla-bin>
> > > 
> > > Then get mozilla to crash.
> > 
> > Excellent!  But, I'm having a hell of a time getting mozilla to build
> > with debugging symbols.  I see -g in the build output, but gdb says
> > there aren't any debugging symbols.  I found a few libs that were left
> > behind by mozilla-embedded that I removed.  Recompiling doesn't seem
> > to help... any ideas on how to get gdb debugging symbols in there?
> > make.conf and my environment have -g set, and I can see the individual
> > object files being compiled with -g.  How can I make mozilla w/o
> > stripping the binary?  -sc
> 
> Add the line:
> 
> STRIP=
> 
> to the mozilla Makefile.

EXCELLENT NEWS!  I found the culprit (roughly).  I moved my .mozilla
file out of the way and had mozilla recreate all of my profile data.
Since then, no problems.  I haven't isolated what it was in my
.mozilla/ dir that did this, but if anyone's curious, let me know and
I'll sanitize and send along a copy.  -sc

-- 
Sean Chittenden

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-ports" in the body of the message




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