Re: Internal compiler error: Bus error
Re: Internal compiler error: Bus error
- Subject: Re: Internal compiler error: Bus error
- From: Jeremy Dronfield <email@hidden>
- Date: Sat, 19 Aug 2006 09:40:44 +0100
On 18 Aug 2006, at 4:39 pm, Shawn Erickson wrote:
On 8/18/06, Tvirlip Tumanov <email@hidden> wrote:
Hi,
> 2.4. I also sometimes get the variation "Internal compiler error:
> Segmentation fault". I haven't submitted a bug report for two
> reasons: Firstly, I'm reluctant to submit the source of a large
> shareware project. But more importantly, the bug seems to be
> completely unpredictable. Sometimes GCC crashes, more often it
> doesn't.
I do not know for sure about Mac OS X, but in Linux/*BSD environment
unpredictable gcc crashes with internal compiler error/segfault
almost for sure mean [slightly] faulty memory (RAM) in a computer. I
saw this many times.
I can confirm that we had our Mac OS X build system (PowerMac Dual G5)
randomly crash while compiling and we traced it down to bad 3rd party
RAM in that particular case. As a result we switched the build system
over to use ECC RAM and so far no reoccurrence of strange gcc crashes
on that system.
Yes, I've heard this about Linux/BSD - I've also heard it could be a
VM issue. Unfortunately I'm not in a position to test, since I don't
have any third-party RAM, nor a second machine. Some people are
suggesting that code issues can trigger it (i.e. syntax problems
which don't necessarily trigger compiler warnings). This chimes with
me, since I have *sometimes* found that altering my code can stop the
crashes (in two cases, removing unnecessary method declarations from
a header file did the trick). But the only magic-bullet seems to be
switching to GCC 3.3.
Jeremy
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden