Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!zaphod.mps.ohio-state.edu!lavaca.uh.edu!menudo.uh.edu!nuchat!sugar!peter From: peter@sugar.hackercorp.com (Peter da Silva) Newsgroups: comp.sys.amiga.programmer Subject: Re: AmigaGCC stack hogging Message-ID: <7672@sugar.hackercorp.com> Date: 31 Jan 91 12:49:23 GMT References: <1882f287.ARN1979@moria.UUCP> <1991Jan14.212254.9779@csun.edu> <18887df5.ARN1ad7@moria.UUCP> <1991Jan17.141218.19953@zorch.SF-Bay.ORG> <17766@cbmvax.commodore.com> Reply-To: peter@sugar.hackercorp.com (Peter da Silva) Organization: Sugar Land Unix - Houston Lines: 11 In article jkh@bambam.pcs.com (Jordan K. Hubbard) writes: > This whole scheme works very nicely under UNIX - It's a pity that processes's > can't seem to automatically grow their stacks during run time. Why is this? The 68000 does not support memory management. You can't detect a stack overflow, or for that matter move a program around (not that that has any breaking on growing a stack on the Amiga: programs are not contiguous) unless you can map memory and trap memory references. -- Peter da Silva. `-_-' .