regchrome causes segfault during Mozilla build

[Patrick C]

On April 10, 2003 12:40 pm, Luke Hollins wrote:
> > > >Release:	FreeBSD 4.8-STABLE i386
> > > >Environment:
> > >
> > > System: FreeBSD octo.sytes.net 4.8-STABLE FreeBSD 4.8-STABLE #4: Wed
> > > Apr 9 14:48:08 MDT 2003
> > > otacon at octo.sytes.net:/usr/obj/usr/src/sys/CONTRA i386
> > >
> > > >Description:
> > >
> > > 	(cd /usr/ports/www/mozilla/work/mozilla/dist/bin;  /usr/bin/env
> > > LD_LIBRARY_PATH=. MOZILLA_FIVE_HOME=. ./regxpcom;  /usr/bin/env
> > > LD_LIBRARY_PATH=. MOZILLA_FIVE_HOME=. ./regchrome;  /usr/bin/touch
> > > ./chrome/user-skins.rdf ./chrome/user-locales.rdf) Segmentation fault
> > > (core dumped)
> > > 	*** Error code 139
> > >
> > > 	I've tried using gcc2.95.4 and gcc3.2.2, both generate the same error,
> > > with or without optimizations. Here are the CFLAGS I've used:
> > > gcc3.2.2:	CFLAGS=-O -pipe -fomit-frame-pointer -mmmx -msse
> > > -march=pentium3 -mcpu=pentium3 gcc2.95.4:	CFLAGS=-O -pipe
> > > -fomit-frame-pointer -march=pentiumpro -mcpu=pentiumpro
> >
> > In the handbook it states that you should not report bugs unless you've
> > built with _default_ CFLAGS.  Please rebuild Mozilla with -O -pipe, and
> > see if the problem persists.
>
> 	I have had the same problem on many machines, removing any
> 	-f and -O options has always fixed it.

Removing -fomit-frame-pointer fixed the regchrome segfault. Mozilla did 
compile with the -O flag left in.

Thanks!