*BSD News Article 24823


Return to BSD News archive

Path: sserve!newshost.anu.edu.au!munnari.oz.au!mel.dit.csiro.au!its.csiro.au!dmssyd.syd.dms.CSIRO.AU!metro!basser.cs.su.oz.au!harbinger.cc.monash.edu.au!yeshua.marcam.com!news.kei.com!ddsw1!library.ucla.edu!europa.eng.gtefsd.com!uunet!nntp.club.cc.cmu.edu!news.sei.cmu.edu!toads.pgh.pa.us!pitt!w2xo!durham
From: durham@w2xo.pgh.pa.us (Jim Durham)
Newsgroups: comp.os.386bsd.bugs
Subject: gcc/ksh bugs
Keywords: gcc ksh bugs
Message-ID: <10@w2xo.pgh.pa.us>
Date: 9 Dec 93 06:03:08 GMT
Lines: 23

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?

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.

I may be hashing over old bugs, but I'd appreciate any info on
these problems.

Thanks,
Jim Durham