Re: Is this a bug in libc6?
In article <[🔎] 8767khi4y3.fsf@tiamat.datasync.com> you wrote:
> ----------------------------------------------------------------------
> 1.6 Definitions of terms
> o Undefined Behaviour -- behaviour, upon the use of a nonportable or
> erroneous program construct, of erroneous data, or of inderminately
> valued objects, for which the standard imposes no
> requirements. Permissible undefined behaviour ranges from ignoring
> the situation completely with unpredictable results, to behaving
> during translation or program execution in a documented manner
> charecteristic of the environment (with or without the issuance of a
> diagnostic message), to terminating a translation or execution (with
> the issuance of a diagnostic message).
> ______________________________________________________________________
> Please show why my statement is incorrect wrt to the above
> statement from the C standard. I said: "Corupting memory is not
> acceptable behaviour! (Unless you document this)". The standard says
> "permissible undefined behaviour ..."
It also says that the standard imposes no requirements.
--
Debian GNU/Linux 1.3 is out! ( http://www.debian.org/ )
Email: Herbert Xu ~{PmV>HI~} <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
--
To UNSUBSCRIBE, email to debian-devel-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Reply to: