Path: utzoo!utgpu!cunews!bnrgate!brtph3!brchh104!brchs1!bnr.ca!rice.edu!sun-spots-request
From: gld@cunixd.cc.columbia.edu (Gary L Dare)
Newsgroups: comp.sys.sun
Subject: Re: Segment violation from malloc (what does it mean?)
Keywords: Miscellaneous
Message-ID: <1161@brchh104.bnr.ca>
Date: 9 Jan 91 21:23:15 GMT
Sender: news@brchh104.bnr.ca
Organization: Sun-Spots
Lines: 20
Approved: Sun-Spots@rice.edu
X-Refs:  Original: v9n353, Replies: v10n3 v10n10
X-Sun-Spots-Digest: Volume 10, Issue 11, message 17
X-Note: Submissions: sun-spots@rice.edu, Admin: sun-spots-request@rice.edu

polar@top.cis.syr.edu (Polar Humenn) writes:
|fredc@umrisca.isc.umr.edu writes:
|>
|>(dbxtool) Running: sym_edit 
|>signal SEGV (no mapping at the fault address) in malloc at 0xec52864
|>malloc+0xe4:		movl	a5@(0xd4),a0
|
|>If so, is it a hardware or un-fixable software limit, or can I get 
|>the compiler to give me a larger heap to work with?
|
|Get a larger swap space.  If your admistrator has extra space he may
|arrange a "swapfile" for you.  However, I'm not really sure if this
|is possible on a diskless client.  

Also, a few strategically free() operations might be in order to clear off
your heap.  Otherwise, stuff you've declared for one-shot use will stick
around after you've exited your routine.

Gary L. Dare
 gld@cunixD.cc.columbia.EDU