home *** CD-ROM | disk | FTP | other *** search
- Path: ra.nrl.navy.mil!usenet
- From: jung@osse.nrl.navy.mil (Greg Jung)
- Newsgroups: comp.sys.amiga.programmer
- Subject: Re: Ceck out this bug. What the *** is SASC/6.56 doing?
- Date: 15 Mar 1996 20:48:56 GMT
- Organization: U.S.R.A/NRL
- Message-ID: <4icl3o$nf1@ra.nrl.navy.mil>
- References: <1120.6643T91T406@login.eunet.no> <4hvk1f$o0c@zeus.central.ntua.gr> <885.6646T9T693@login.eunet.no>
- NNTP-Posting-Host: ossep2.nrl.navy.mil
- Mime-Version: 1.0
- X-Newsreader: WinVN 0.99.3
-
- In article <885.6646T9T693@login.eunet.no>,
- patrick.hanevold@login.eunet.no says...
- >
- >
- >>>Tryed "Stack check" and all that. No difference.
- >>>Anyway, the default stack is 4K isnt it?
- >>>Cant think of anything using that additional 1K.
- >>>Dont want it global. Allocate it myself now.
- Just try doing it with "stack 20000" from the CLI, then its a
- stack problem, what's the big deal? You think you're the first
- to accuse a compiler of a bug it never had? You think you'll
- be the last?
- >>>
- >>OpenScreenTags() need stack too!! Together with the already used stack
- >>by _main, and the 3252 bytes of main(), you only have about 800 bytes
- >>left for OpenScreenTags(), might be too small. Stackcheck will not
- >>find this, because stackcheck does not know the stack-usage of
- >>OpenScreenTags().
- >
- >OpenScreenTags() doesnt crash. exit(0) does.
- >I guess it maby could mess up so exit(0) would crash.
- >Stach check should be smart enough to fail if there was too litle stack
- left.
- >I would guess none of the OS calls would need more then 4K since thats
- the
- >default stack size.
- >
- The default stack size can be changed, and probably is at 4k for the
- minimum to run out-of-box sw. So now you know what stack is, go ye
- and code some more. Bring us something worthy of thy name! Just
- stop the incredibly stubborn posturing we see in later posts.
-
- Greg Jung
-
-