*BSD News Article 24854


Return to BSD News archive

Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!elroy.jpl.nasa.gov!swrinde!cs.utexas.edu!uunet!EU.net!ieunet!news.ieunet.ie!jkh
From: jkh@whisker.lotus.ie (Jordan K. Hubbard)
Newsgroups: comp.os.386bsd.bugs
Subject: Re: gcc/ksh bugs
Date: 10 Dec 1993 00:39:39 GMT
Organization: Dublin, Ireland
Lines: 16
Distribution: world
Message-ID: <JKH.93Dec9163939@whisker.lotus.ie>
References: <10@w2xo.pgh.pa.us>
NNTP-Posting-Host: whisker.lotus.ie
In-reply-to: durham@w2xo.pgh.pa.us's message of 9 Dec 93 06:03:08 GMT

In article <10@w2xo.pgh.pa.us> durham@w2xo.pgh.pa.us (Jim Durham) writes:
   Gcc crashes with signal 10 and signal 11. These are "BUS ERROR"
   and "SEGMENTATION VIOLATION". There seems to be no logical pattern to
   these occurences. Sometimes , while compiling a particular C
   source file, gcc will die with signal 10, the, upon trying again on the
   same source file, it will die with signal 11, then , on another try, it
   will compile. Sounds like an unitialized pointer somewhere in gcc, for
   a guess. Anyone else had this problem?

Are you running on a 4MB system?  FreeBSD 1.0 has known problems with
4MB systems.  Your solution is to wait for 1.1, or get another 4MB
of memory! :-)

					Jordan
--
(Jordan K. Hubbard)  jkh@violet.berkeley.edu, jkh@al.org, jkh@whisker.lotus.ie