Return to BSD News archive
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!msunews!uchinews!vixen.cso.uiuc.edu!howland.reston.ans.net!news.sprintlink.net!hookup!solaris.cc.vt.edu!news.mathworks.com!panix!cmcl2!CS.Arizona.EDU!not-for-mail From: dave@CS.Arizona.EDU (Dave Schaumann) Newsgroups: comp.unix.bsd.netbsd.misc Subject: Re: Segmentation fault - Running out of memory? Date: 11 Mar 1995 01:29:49 -0700 Organization: University of Arizona CS Department, Tucson AZ Lines: 19 Message-ID: <3jrn1t$813@lectura.CS.Arizona.EDU> References: <jds-0803952113340001@199.33.147.50> NNTP-Posting-Host: lectura.cs.arizona.edu In article <jds-0803952113340001@199.33.147.50>, John D. Smerdon <jds@smerdon.plymouth.mi.us> wrote: >Segmentation fault - core dumped >*** Error code 139 > >Is that how "out of memory" is reported on a system It's certainly possible that an out-of-memory situation could cause your compiler to segfault (an unfortunately large number of unix tools seem to not bother checking if malloc returns NULL...) >or is there something else wrong? That's the alternative. I'd check your memory situation first. -Dave -- No sniveling.