maybe it could be an error related to parity fault of RAM modules ?

rj45


On Thu, 20 Jul 2000, Andrew Sporner wrote:

> Hi
> 
> I have seen this many times and a healthy reboot
> has cleared it up in most cases.  This is an Illegal
> instruction trap.  What I used to get where segmentation
> faults, which were very random, but always removed after
> a reboot.  In many cases after some delay, the problem
> would resurface.  This was back in 1.3 time frame, so 
> I am not sure if this is the same problem you are having.
> 
> 
> Andy
> 
> 
> > -----Original Message-----
> > From: rj45 [mailto:rj45@lart.xmission.com]
> > Sent: Thursday, July 20, 2000 10:43 AM
> > To: port-vax@netbsd.org
> > Subject: cc1 compiler error.
> > 
> > 
> > 
> > I Am compiling imlib 1.9.8
> > 
> > I got this strange error
> > 
> > cc -O2 -I/usr/pkg/include -I/usr/X11R6/include 
> > -I/usr/pkg/lib/glib/include
> > -I/usr/pkg/include/glib -I/usr/X11R6/include -I/usr/X11R6/include
> > -I/usr/X11R6/include -c testimg.c
> > cc: Internal compiler error: program cc1 got fatal signal 4
> > 
> > could someone help me understanding this thing ??
> > 
> > thanks
> > 
> > rj45
> > 
> > 
>