home *** CD-ROM | disk | FTP | other *** search
- Path: Norway.EU.net!usenet
- From: patrick.hanevold@login.eunet.no (Patrick Hanevold)
- Newsgroups: comp.sys.amiga.programmer
- Subject: Re: Ceck out this bug. What the *** is SASC/6.56 doing?
- Date: 15 Mar 1996 18:22:21 GMT
- Organization: EUnet Norway
- Message-ID: <1621.6647T1143T325@login.eunet.no>
- References: <1120.6643T91T406@login.eunet.no> <v24trvir4v.fsf@athena-e.eurpd.csg.mot.com>
- <879.6646T4T2378@login.eunet.no> <Do9Gpy.Juv@unx.sas.com>
- NNTP-Posting-Host: pc3.asker-pm2-1.eunet.no
- X-Newsreader: THOR 2.22 (Amiga;TCP/IP)
-
-
- >The SAS/C stack check routines are performing exactly as documented and
- >exactly as designed. They are doing everything it is reasonable to expect
- >them to do, namely, make sure that the function compiled with stack checking
- >has enough stack for its use. If you think it is possible for the compiler
- >to protect your program against every stupid thing it tries to do, you are
- >sadly mistaken. The responsibility to make sure your program behaves
- >intelligently is yours, not the compiler's. I suggest you read the section
- >of the manual devoted to disussion stack checking, stack extension, and
- >the runtime architecture of a C program.
-
- Stil think the deafult minimum stack size is way to small.
-
- >>Anyway, none of the OS calls themseves crash. Its SC's exit routines
- >>that messes around in memory. Avent checked so much whats going on around
- >>there, but it shouldnt crash with stack check or stack extend on.
-
- >With a stack trash, it is quite likely that nothing bad would happen
- >before the program exits. It all depends on what is lying around in
- >memory that happened to get trashed when the stack was overrun.
-
- Yup. Strange non of the other tasks went bagawonga thoug. :)
-
- -----------------------------------------------------------------------------
- Patrick Hanevold - VR developer - patrick.hanevold@login.eunet.no
- Silicon Graphics Power Onyx system with four R8000 processors and two
- Reality Engine 2s. 5 gigabytes of RAM. 200 gigabytes of fast disk
- (single-file optimized read rate of 250 megabytes/sec).
- --------------------- But heck, my Amy boots faster. :) ---------------------
-
-