This is the mail archive of the gcc-help@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: What can cause a "Memory fault"

From: Ian Lance Taylor <ian at airs dot com>
To: corey taylor <corey dot taylor at gmail dot com>
Cc: Hamilton Chris-cham <chris dot hamilton at freescale dot com>, "gcc-help at gcc dot gnu dot org" <gcc-help at gcc dot gnu dot org>
Date: 29 Mar 2005 11:39:33 -0500
Subject: Re: What can cause a "Memory fault"
References: <E99F8A66B3F8D8119BAC000F20D7A41408B846BD@az33exm41.am.freescale.net><m3r7hymmy8.fsf@gossamer.airs.com><2e393d08050329083638e5e5f1@mail.gmail.com>

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

Follow-Ups:
- Re: What can cause a "Memory fault"
  - From: corey taylor

References:
- What can cause a "Memory fault"
  - From: Hamilton Chris-cham
- Re: What can cause a "Memory fault"
  - From: Ian Lance Taylor
- Re: What can cause a "Memory fault"
  - From: corey taylor

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]