Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion Groups
General
GeneralPortable MacsHardwareNetworking
Applications
Mac ApplicationsEudoraFirefox / MozillaInternet ExplorerOutlook ExpressMS OfficeEntourageExcelPowerPointWordVirtual PCMedia PlayerOther MS Products
Programming
Mac ProgrammingCodeWarriorPerl
Country Specific
Australian Mac GroupUK Mac Group

Mac Forum / Programming / Mac Programming / November 2006



Tip: Looking for answers? Try searching our database.

XCode/GCC keeps throwing bus errors

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
RogueWarrior - 07 Oct 2006 01:39 GMT
It must be a full moon or something.  GCC keeps throwing bus errors.  I
restart compiling and it continues but a while later it throws it
again.  And LD throws segmentation faults.  Does anyone know why this
is happening?
toby - 07 Oct 2006 08:03 GMT
> It must be a full moon or something.  GCC keeps throwing bus errors.  I
> restart compiling and it continues but a while later it throws it
> again.  And LD throws segmentation faults.  Does anyone know why this
> is happening?

Tested your memory lately? (Other than by running a compiler...)
RogueWarrior - 07 Oct 2006 16:11 GMT
> Tested your memory lately? (Other than by running a compiler...)

Actually I did.  I looked on the Apple lists for this issue and that
was suggested several times so I dutifully purchased the latest version
of Memtest.  Here's where it gets a little strange.  The first time I
ran it, it allocated something less than a quarter my RAM (2GB).   The
second time I ran it it was less than half.  Running "top" said that
something like 1.6 gig was in use.  I wasn't running anything other
than OSX and Terminal.  So I figured a reboot might help.  Now I was
able to allocate nearly all the RAM and test it several times all with
no errors whatsoever.  And guess what.  GCC compiled without a hitch.
Over 2000 files.  Weird.
Santa Claus - 26 Nov 2006 05:58 GMT
> > Tested your memory lately? (Other than by running a compiler...)
>
[quoted text clipped - 8 lines]
> no errors whatsoever.  And guess what.  GCC compiled without a hitch.
> Over 2000 files.  Weird.

here's another thing you can do, i noticed that for some reason GCC encounters bus errors ONLY during the optimization phase so if you turn off optimization, it should compile at least.  it seems that running out of memory throws GCC into bus error or internal compiler error.
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.