RE: What can cause a "Memory fault"

RE: What can cause a "Memory fault"

[Hamilton Chris-cham]

I've never been able to get any compiler built on this AMD platform.  For bootstrap compiler, I've tried using another compiler I built on a 32-bit Linux platform (not this AMD platform), and I've also tried the compiler that was distributed with this AMD machine.

I haven't read a lot about bad RAM, but I had the impression that if you had bad RAM, your failures wouldn't be so predictable.  In my case, the failure happens predictably at the same spot every time (assuming I don't change the configuration).

How can I prove whether this is a memory problem?

Chris

> -----Original Message-----
> From: corey taylor [mailto:corey.taylor@gmail.com] 
> Sent: Tuesday, March 29, 2005 10:45 AM
> To: Ian Lance Taylor
> Cc: Hamilton Chris-cham; gcc-help@gcc.gnu.org
> Subject: Re: What can cause a "Memory fault"
> 
> 
> Chris,
> 
>   Correct me if I'm wrong, but when we first talked, weren't you able
> to compile a bootstrap at some point and only compiling 3.4.3 was
> causing issues?
> 
> corey
> 
> 
> On 29 Mar 2005 11:39:33 -0500, Ian Lance Taylor <ian@airs.com> wrote:
> > corey taylor <corey.taylor@gmail.com> writes:
> > 
> > > This user's question yesterday explains the issue in more detail:
> > >
> > > http://gcc.gnu.org/ml/gcc-help/2005-03/msg00251.html
> > 
> > Thanks.
> > 
> > That does look more like bad RAM than a compiler bug.  It could
> > possibly be a ksh bug or a linker bug.
> > 
> > Ian
> >
> 

Re: What can cause a "Memory fault"

[Ian Lance Taylor]

Hamilton Chris-cham <chris.hamilton@freescale.com> writes:

> I haven't read a lot about bad RAM, but I had the impression that if
> you had bad RAM, your failures wouldn't be so predictable.  In my
> case, the failure happens predictably at the same spot every time
> (assuming I don't change the configuration).

I agree that that seems less likely to be a RAM problem, although it
is certainly still possible.

> How can I prove whether this is a memory problem?

Run a memory tester, such as http://www.memtest86.com/  I don't know
whether that will work on an x86-64 platform, but it may.  Or AMD may
provide one with the system.

But first see if you can run the failing command manually, and have it
fail in the same way.  If you can, add -xv options to ksh to see
precisely which command is failing.  That may help.

Ian

Re: What can cause a "Memory fault"

[corey taylor]

Chris,

  Correct me if I'm wrong, but when we first talked, weren't you able
to compile a bootstrap at some point and only compiling 3.4.3 was
causing issues?

corey


On 29 Mar 2005 11:39:33 -0500, Ian Lance Taylor <ian@airs.com> wrote:
> corey taylor <corey.taylor@gmail.com> writes:
> 
> > This user's question yesterday explains the issue in more detail:
> >
> > http://gcc.gnu.org/ml/gcc-help/2005-03/msg00251.html
> 
> Thanks.
> 
> That does look more like bad RAM than a compiler bug.  It could
> possibly be a ksh bug or a linker bug.
> 
> Ian
>

Re: What can cause a "Memory fault"

[Ian Lance Taylor]

corey taylor <corey.taylor@gmail.com> writes:

> This user's question yesterday explains the issue in more detail:
> 
> http://gcc.gnu.org/ml/gcc-help/2005-03/msg00251.html

Thanks.

That does look more like bad RAM than a compiler bug.  It could
possibly be a ksh bug or a linker bug.

Ian

Re: What can cause a "Memory fault"

[corey taylor]

This user's question yesterday explains the issue in more detail:

http://gcc.gnu.org/ml/gcc-help/2005-03/msg00251.html

corey


On 29 Mar 2005 11:33:19 -0500, Ian Lance Taylor <ian@airs.com> wrote:
> Hamilton Chris-cham <chris.hamilton@freescale.com> writes:
> 
> > I'm having problems building GCC 3.4.3 on a 64-bit AMD Athlon Linux machine.  My bootstrap fails with a "Memory fault" error message.  What can cause this message?
> 
> 1) A compiler bug.
> 
> 2) Bad RAM in your system.
> 
> There are probably other possibilities, but it's hard to say with so
> little information.
> 
> Ian
>

Re: What can cause a "Memory fault"

[Ian Lance Taylor]

Hamilton Chris-cham <chris.hamilton@freescale.com> writes:

> I'm having problems building GCC 3.4.3 on a 64-bit AMD Athlon Linux machine.  My bootstrap fails with a "Memory fault" error message.  What can cause this message?

1) A compiler bug.

2) Bad RAM in your system.

There are probably other possibilities, but it's hard to say with so
little information.

Ian

What can cause a "Memory fault"

[Hamilton Chris-cham]

I'm having problems building GCC 3.4.3 on a 64-bit AMD Athlon Linux machine.  My bootstrap fails with a "Memory fault" error message.  What can cause this message?