home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.amiga.programmer
- Path: mozart.unx.sas.com!sassek
- From: sassek@unx.sas.com (Steve Krueger)
- Subject: Re: Ceck out this bug. What the *** is SASC/6.56 doing?
- Sender: news@unx.sas.com (Noter of Newsworthy Events)
- Message-ID: <sassek.826554207@sas.com>
- Date: Mon, 11 Mar 1996 14:23:27 GMT
- X-Nntp-Posting-Host: wonka.unx.sas.com
- References: <1120.6643T91T406@login.eunet.no>
- Organization: SAS Institute Inc.
-
- patrick.hanevold@login.eunet.no (Patrick Hanevold) writes:
-
-
- >Can anyone explain this? Try compiling this with a SC default SCOPTIONS
- >file, and start it from CLI. It only crashes from CLI.
- >This one was REALY fun finding. Dealyed ChunkyScreen a couple of days.
-
- >void main(void)
- >{
- > int x,y,n;
- > UBYTE Buffer[ScreenWidth];
- > ULONG Palette[256*3+2]; // This one causes the bug.
-
- > struct Screen *Scr=OpenScreenTags(NULL,
- > SA_Width, 320,
- > SA_Height, 256,
- > SA_Depth, 8,
- > TAG_END);
-
- > CloseScreen(Scr);
- >}
-
- You are probably running out of stack. With a standard 4k stack,
- after the prolog of main(), you only have 640 bytes of stack left.
- Apparently not enough for OpenScreenTags(). The program runs
- fine with a 20k stack.
-
- sk
-