Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!tut.cis.ohio-state.edu!dsac.dla.mil!dsacg3.dsac.dla.mil!nfs1675
From: nfs1675@dsacg3.dsac.dla.mil ( Michael S Figg)
Newsgroups: comp.sys.amiga.tech
Subject: Re: stack setting?
Summary: Seperate process
Message-ID: <2289@dsacg3.dsac.dla.mil>
Date: 3 Jul 90 17:08:06 GMT
References: <13580002@hpspdra.HP.COM>
Organization: Defense Logistics Agency Systems Automation Center, Columbus
Lines: 31

In article <13580002@hpspdra.HP.COM>, ric@hpspdra.HP.COM (Ric Peregrino) writes:
> I have ported a wave editor program to the amiga and found that the 
> default stack of 4000 is too small. I tried using a system call in
> the program to automatically set the stack, but it seems to fail.
> Anybody know why this is, or how it can be done? 
> 
> printf("setting stack to 8192\n");
> system("stack 8192");
> system("stack");
> 
> ric@hpspd

My experience is alittle limited but I've been studying this lately. I believe
that 'stack' only sets the stack for the current process and each of your
'system' calls is a seperate process besides your program itself. You could
set it first from the shell or have a script driving your wave editor which
would set the stack first. The stack is only memory for your program to use so
you should also be able to do a 'malloc' but I'm not sure how you would 
allocate this just for the stack. 

Am I making any sense here? Could someone explain this better so I understand
it also!

---Mike


-- 
A man said to the Universe "Sir, I exist!" | Michael Figg  DSAC-FSD
"However," replied the Universe,           | DLA Systems Automation Center
"The fact has not created in me a          | Columbus, Ohio
sense of obligation."- Stephen Crane       | mfigg@dsac.dla.mil  CIS: 73777,360