Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!sdd.hp.com!decwrl!shelby!agate!ucbvax!GODZILLA.CGL.RMIT.OZ.AU!angus
From: angus@GODZILLA.CGL.RMIT.OZ.AU ("Angus Y. Montgomery")
Newsgroups: comp.sys.sgi
Subject: does anyone know about this strange malloc failure?
Message-ID: <9101240730.18093@godzilla.cgl.rmit.oz.au>
Date: 24 Jan 91 22:30:14 GMT
Sender: usenet@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 20


Running some software that is perfectly OK on another MIPS platform, and
somewhere along the way malloc causes this error:

WARNING: Process [a.out] pid 17019 sent SIGSEGV because it exceeded its maximum 
process/stack size

:it's not the first time that malloc is called in the run.
:the stack and data spaces are both large enough (2^19 Kb) that there
   is no way i can conceive of that this relatively small process
   should run out of space.
:we've tried using the other malloc from <malloc.h> and also using mallopt
   to make sure free-ed memory was still usable in case space was prematurely
   freed

all to (obviously) no avail.
anyone else have/had this problem, a solution, or even a wild guess
could they please tell me.
thanx.
angus@godzilla.cgl.rmit.oz.au