Return to BSD News archive
Path: sserve!manuel!munnari.oz.au!spool.mu.edu!uunet!elroy.jpl.nasa.gov!sdd.hp.com!uakari.primate.wisc.edu!usenet.coe.montana.edu!news.u.washington.edu!ogicse!network.ucsd.edu!qualcom.qualcomm.com!servo.qualcomm.com!karn From: karn@servo.qualcomm.com (Phil Karn) Newsgroups: comp.unix.bsd Subject: Re: strtod.c -- Where's the source Luke? Message-ID: <1992Sep18.154311.20396@qualcomm.com> Date: 18 Sep 92 15:43:11 GMT Article-I.D.: qualcomm.1992Sep18.154311.20396 References: <8851@hq.hq.af.mil> <DJM.92Sep15104153@frob.eng.umd.edu> Sender: news@qualcomm.com Organization: Qualcomm, Inc Lines: 19 Nntp-Posting-Host: servo.qualcomm.com In article <DJM.92Sep15104153@frob.eng.umd.edu> djm@eng.umd.edu (David J. MacKenzie) writes: >You can get strtod.c from the GNU shellutils 1.7, but when I tried >compiling it on 386BSD 0.1, gcc died from some internal error, with >signal 6 I think. I didn't try to figure out what it was about the >file that tickled the compiler bug; I just gave up. Signal 6 is an abort() call, i.e., the compiler committed suicide. I frequently ran into the same problem with GCC when I first brought up 386BSD, and I'm pretty sure it's triggered by the compiler running out of memory (ie., it attempts a malloc() which returns NULL). The default 386BSD file system allows only 5 megabytes of disk space for a swap area, and this is apparently too small for large compiles. Last night I regenerated my 386BSD system with 50 megabytes of swap space, and compiles that previously bombed now work (or at least they don't bomb with signal 6s!) Phil