From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.3 required=5.0 tests=BAYES_00,INVALID_MSGID
	autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 1014db,dab7d920e4340f12
X-Google-Attributes: gid1014db,public
X-Google-Thread: 103376,dab7d920e4340f12
X-Google-Attributes: gid103376,public
From: token%/etc/HOSTNAME (Matthias Buelow)
Subject: Re: C is 'better' than Ada because...
Date: 1996/06/24
Message-ID: <4qm3c4$iv4@winx03.informatik.uni-wuerzburg.de>#1/1
X-Deja-AN: 161835219
references: <4q8fbo$701@red.interact.net.au> <nhk9wzyjn3.fsf@paralysys>
 <31CC75C1.5BF2AF6A@jinx.sckans.edu> <dewar.835489134@schonberg>
 <Pine.LNX.3.92.960623122941.795A-100000@switch.sp.org>
followup-to: comp.lang.c,comp.lang.ada
organization: University of Wuerzburg, Germany
newsgroups: comp.lang.c,comp.lang.ada
Date: 1996-06-24T00:00:00+00:00
List-Id: <comp.lang.ada>


The Deviant (deviant@sp.org) wrote:

: But, the variable was initialized as

: char blah[5];

: which means it goes out of its bouts as soon as it tries to access
: blah[5], and thats when SIGSEGV, by definition, should occur.

Would you please share your enlightenment concerning the correct definition
of when SIGSEGV should occur? I only know that it's completely architecture
and OS-dependant.
If the array lies in a memory-page/segment/whatever that is accessible and 
writeable by the program, there will be no violation fault instantly but 
only after the program has executed a bit further and the side effect of
the above operation is causing trouble.  SIGSEGV is a hardware-triggered
thing and not part of a language definition.

--
    Matthias `Token' Buelow    @ Home: token@altair.franken.de  (PGP avail.)
                               Campus: token@cip.informatik.uni-wuerzburg.de