home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!europa.asd.contel.com!darwin.sura.net!zaphod.mps.ohio-state.edu!cs.utexas.edu!qt.cs.utexas.edu!news.Brown.EDU!noc.near.net!news.centerline.com!matt
- From: matt@centerline.com (Matt Landau)
- Newsgroups: comp.lang.c++
- Subject: Re: something nasty
- Date: 13 Nov 1992 06:58:47 GMT
- Organization: CenterLine Software, Inc.
- Lines: 22
- Message-ID: <1dvjn7INNhrs@armory.centerline.com>
- References: <1992Nov06.105523.3309@ncrcae.ColumbiaSC.NCR.COM> <1992Nov9.171715.20728@sierra.com> <1992Nov13.050829.952@BofA.com>
- NNTP-Posting-Host: 140.239.1.32
-
- In <1992Nov13.050829.952@BofA.com> dan@BofA.com (Dan Brockman) writes:
-
- >I have received much correspondence of late regarding
- >error message "...bus error or something nasty...". Many
- >have seen it, and each seems to have traced it to a different
- >specific problem. No strong patterns. Many suggested
- >"get another compiler".
-
- That's because there *is* no one specific cause of the problem.
-
- The message you're seeing is cfront's all-purpose error message for
- situations when things go awry and the C++ translator either crashes
- or gives up due to internal errors of some sort.
-
- In my own experience, I've tended to see internal errors when trying to
- compile expressions that are too complicated for cfront (which you can
- often deal with by finding the offending expression and simplifying it,
- splitting into multiple statements and introducing explicit temporaries
- as needed), and pushing too hard on nested classes in cfront 2.1.x
- --
- Matt Landau Waiting for a flash of enlightenment
- matt@centerline.com in all this blood and thunder
-