Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!elroy.jpl.nasa.gov!usc!rutgers!cbmvax!higgin
From: higgin@cbmvax.commodore.com (Paul Higginbottom - CATS)
Newsgroups: comp.sys.amiga.programmer
Subject: Re: Setting the Stack
Message-ID: <17603@cbmvax.commodore.com>
Date: 15 Jan 91 15:50:33 GMT
References: <MACDON.91Jan14161303@beach.csulb.edu> <3589@bruce.cs.monash.OZ.AU>
Reply-To: higgin@cbmvax.commodore.com (Paul Higginbottom - CATS)
Organization: Commodore, West Chester, PA
Lines: 19

In article <3589@bruce.cs.monash.OZ.AU> roddi@bruce.cs.monash.OZ.AU (Roddi Walker) writes:
$	I want to set my stack to 100,000 bytes (I've got mountains of
$RAM), so I accordingly put the line 'stack 100000' into my
$startup-sequence.
$	The weird thing is that when I type 'stack' from a CLI to
$query the stack size, it report 4000 - the default size.
$	I seems that my stack size is somehow being reset, perhaps
$by something in my startup-sequence.  Can anyone out there shed
$some light on this?

You're probably setting the stack AFTER you do LoadWB, and thus
Workbench is launching a new shell or cli with the default 4000
byte stack space.

Another thing you can do since you may not want EVERY process getting
100K is to simply put it in your s:Shell-Startup file so that each
shell gets 100K of stack.

	Paul.