Date: Fri, 12 Aug 2005 19:55:20 +0200 From: "albi@scii.nl" <albi@scii.nl> To: freebsd-questions@freebsd.org Subject: Re: FREEBSD 5.4 - Internal compiler error: Segmentation fault Message-ID: <20050812195520.600ebbc6.albi@scii.nl> In-Reply-To: <42FCE0B4.1010301@u.washington.edu> References: <BAY101-F7F697344216330944F84DF7BC0@phx.gbl> <42FCE0B4.1010301@u.washington.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 12 Aug 2005 10:47:32 -0700 Garrett Cooper <youshi10@u.washington.edu> wrote: > > ../../gcc/gcc/calls.c:1693: internal compiler error: Segmentation fault > > Please submit a full bug report, > > with preprocessed source if appropriate. > > See <URL:http://gcc.gnu.org/bugs.html>; for instructions. > > gmake[1]: *** [calls.o] Error 1 > > gmake[1]: Leaving directory > > `/usr/ports/lang/ezm3/work/ezm3-1.2/language/modula3/m3compiler/m3cc/FreeBSD4/gcc' -- cut -- > > Stop in /usr/ports/net/cvsup-without-gui. > > Dunno if this applies to FBSD as well, but in Linux many GCC seg faults > were caused by either bad programming on someone's behalf, or bad RAM. > I'd run a RAM test first just to be sure it's not the RAM either that or cooling-problems are possible, did you (OP) see any signal 11 messages in your logfiles ?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050812195520.600ebbc6.albi>