Return to BSD News archive
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!newshost.marcam.com!zip.eecs.umich.edu!umcc.umich.edu!smerdon.plymouth.mi.us!user From: jds@smerdon.plymouth.mi.us (John D. Smerdon) Newsgroups: comp.unix.bsd.netbsd.misc Subject: Segmentation fault - Running out of memory? Date: Wed, 08 Mar 1995 21:13:34 -0500 Organization: Home Lines: 24 Distribution: world Message-ID: <jds-0803952113340001@199.33.147.50> NNTP-Posting-Host: ppp01.smerdon2.plymouth.mi.us While doing a "make build" on a Macintosh SE/30 (8MB phys/32MB swap, 1.0A from around 02/15) I got this: cc -O -DNLS -DYP -DLIBC_SCCS -DSYSLIBC_SCCS -I/usr/src/lib/libc/include -D__DBINTERFACE_PRIVATE -DPOSIX_MISTAKE -DFLOATING_POINT -c -fpic -DPIC /usr/src/lib/libc/stdio/fgetc.c -o fgetc.so Segmentation fault - core dumped *** Error code 139 Is that how "out of memory" is reported on a system or is there something else wrong? I usually see 5-6MB of swap used from a "pstat -s". Sometimes it goes up to 12-16MB during a compile. After, I did something like "csh; unlimit; make build" and it completed and installed without errors. Out of curiosity, does it take everyone else three to four days to do a "make build"? :-) -- John D. Smerdon; Plymouth, Michigan, USA; Contents are my opinion. Home: jds@smerdon.plymouth.mi.us