RE: Compiler segmentation fault in 5-08 -CURRENT

   

> -----Original Message-----
> From: owner-freebsd-current_at_freebsd.org 
> [mailto:owner-freebsd-current_at_freebsd.org] On Behalf Of 
> Terrence Koeman
> > -----Original Message-----
> > From: owner-freebsd-current_at_freebsd.org 
> > [mailto:owner-freebsd-current_at_freebsd.org] On Behalf Of Doug White
> > 
> > On Tue, 10 Aug 2004, Terrence Koeman wrote:
> > 
> > > > Can you compile a simple "hello world" program?  Sometimes
> > > > these types of
> > > > faults can be caused by faulty memory, processor, 
> overclocking, or
> > > > temperature issues.
> > >
> > > It doesn't seem hardware related. Before the update I had 
> > no problems with
> > > segmentation faults, and the system can take heavy load just fine.
> > >
> > > I tried to compile the following hello world program:
> > [...]
> > > helloworld.c:4: internal compiler error: Segmentation fault
> > 
> > Ugh. Looks like your gcc binary's busted.
> > 
> > > Is there perhaps a way to copy over the compiler from a 
> > working (older)
> > > -CURRENT system and build a new world with it to see if 
> > it's fixed in cvs?
> > 
> > You might try tracking down a recent snapshot and do an 
> > 'upgrade'; that
> > should overwrite your defective binary.
> > 
> > This problem is unique to you so you may have had a disk error or
> > something that's zeroed out part of the gcc binary or cc1 
> or something
> > important like that.
> 
> I have copied over /usr/bin/* from another working system and 
> now I can
> compile things again.
> 
> Is there anything that could create new problems when doing this?
> 

Well, it seems to be fixed now. As I said I copied over the /usr/bin dir
from another system and build world with it. It gave a shitload of warnings
I've never seen, but it proceeded anyway.

Thanks for your help, I didn't think of a corrupted binary.

-- 
Regards,
Terrence Koeman
 
MediaMonks B.V. (www.mediamonks.com)
Please quote all replies in correspondence.