Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!sgiblab!cs.uoregon.edu!news.uoregon.edu!usenet.coe.montana.edu!bsd.coe.montana.edu!nate From: nate@bsd.coe.montana.edu (Nate Williams) Newsgroups: comp.os.386bsd.bugs Subject: Re: gcc/ksh bugs Date: 9 Dec 1993 17:39:52 GMT Organization: Montana State University, Bozeman MT Lines: 33 Message-ID: <2e7nt8$c4m@pdq.coe.montana.edu> References: <10@w2xo.pgh.pa.us> NNTP-Posting-Host: bsd.coe.montana.edu Keywords: gcc ksh bugs In article <10@w2xo.pgh.pa.us>, Jim Durham <durham@w2xo.pgh.pa.us> wrote: >Hello, > >I'm a new FreeBSD user, but not new to BSD, as I am an Ultrix user. > >I have been having trouble with gcc and ksh. > >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? How much memory do you have? If you have more than 4MB, this sounds like a bad motherboard/cache problem. >The ksh binary from freebsd.cdrom.com works fine, except that >if you pipe the output of a command like "sed" to a file, it writes >a bizillion nulls to the front of the file. No idea. Nate -- nate@bsd.coe.montana.edu | Freely available *nix clones benefit everyone, nate@cs.montana.edu | so let's not compete with each other, let's work #: (406) 994-4836 | compete with folks who try to tie us down to home #: (406) 586-0579 | proprietary O.S.'s (Microsloth) - Me