Date: Fri, 01 Apr 2005 13:38:19 +0200 From: Jiri Novak <novak@nostromo.cz> To: freebsd-questions@freebsd.org Subject: Re: segfaulting gcc Message-ID: <d2jbor$avp$1@sea.gmane.org> In-Reply-To: <424D3033.6050409@dial.pipex.com> References: <d2j8ap$jk$1@sea.gmane.org> <424D3033.6050409@dial.pipex.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Alex Zbyslaw wrote: > Jiri Novak wrote: > >> and I have noticed that lots of ports fail to build because of >> "internal compiler error" from GCC... > > > Does the error always occur in the same place? If not, then it is > possible you have a hardware fault. > > A segmentation fault results from bad memory access, which could be a > program(mer) fault, but in something as well developed as GCC, they > ought never to happen. > > If it is a hardware fault, the likely culprits are memory and disk. Do > you have any interesting messages in /var/log/messages? > > --Alex The error always occur at the same place, in ports (it was firefox and mplayer for sure, not quite sure about others) and in buildworld, so I don't suspect faulty hardware. No useful messages in /var/log/messages... Well, it seems that I'm doomed :( -- Jiri Novak
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?d2jbor$avp$1>