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.9 required=5.0 tests=BAYES_00,FREEMAIL_FROM
	autolearn=ham autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,e6a2e4a4c0d7d8a6
X-Google-Attributes: gid103376,public
X-Google-ArrivalTime: 2003-02-28 20:54:27 PST
Path: 
 archiver1.google.com!news1.google.com!newsfeed.stanford.edu!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!out.nntp.be!propagator2-SanJose!in.nntp.be!newsfeed01.tsnz.net!news.xtra.co.nz!53ab2750!not-for-mail
From: "AG" <ang@xtra.co.nz>
Newsgroups: comp.lang.ada
References: <mHZ0a.42983$jM5.108891@newsfeeds.bigpond.com>
 <nRg1a.190899$HG.32437469@news4.srv.hcvlny.cv.net>
 <3E51908E.9CCA3412@adaworks.com>
 <8Gh4a.7455$_c6.743959@newsread2.prod.itd.earthlink.net>
 <3E51ABCE.5491B9A2@adaworks.com> <b2spe6$p23$1@helle.btinternet.com>
 <3E5273DE.2050206@cox.net> <3E531E6F.BDFB2599@adaworks.com>
 <3E546C45.4010406@cox.net> <3E54F926.441D5BB5@adaworks.com>
 <1045763933.848350@master.nyc.kbcfp.com>
 <42EA55F4BE83950E.F1DA277C2FDC157B.C804C1C52FE95D65@lp.airnews.net>
 <1045769690.126389@master.nyc.kbcfp.com> <2lb33b.7d6.ln@jellix.jlfencey.com>
 <1045772065.590669@master.nyc.kbcfp.com> <oprkxqhntnmzo9uz@news.vol.cz>
 <1045839283.86671@master.nyc.kbcfp.com> <v5d4ecdfopogde@corp.supernews.com>
 <slrnb5embn.le.randhol+news@kiuk0152.chembio.ntnu.no>
 <v5kv6ub5oj0299@corp.supernews.com>
 <slrnb5mfjo.o4.randhol+news@kiuk0152.chembio.ntnu.no>
 <uadgi6foa.fsf@nasa.gov>
Subject: Re: status of PL/I as a viable language
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Message-ID: <62X7a.112770$F63.2427389@news.xtra.co.nz>
Date: Sat, 1 Mar 2003 17:56:35 -0800
NNTP-Posting-Host: 219.88.60.27
X-Complaints-To: newsadmin@xtra.co.nz
X-Trace: news.xtra.co.nz 1046494466 219.88.60.27 (Sat,
 01 Mar 2003 17:54:26 NZDT)
NNTP-Posting-Date: Sat, 01 Mar 2003 17:54:26 NZDT
Organization: Xtra
Xref: archiver1.google.com comp.lang.ada:34756
Date: 2003-03-01T17:56:35-08:00
List-Id: <comp.lang.ada>


"Stephen Leake" <Stephen.A.Leake@nasa.gov> wrote in message
news:uadgi6foa.fsf@nasa.gov...

> I think the English meaning of the term "buffer overflow" is clear;
> the program tried to write more data to the buffer than it had room
> for.

So much for the precision of the English language :)
To me, "buffer overflow" means that whatever tried
to write into it went over the buffer boundaries.

Never mind the amount of data etc etc - the whole
point of the definition is that the data went [or tried
to go] beyond the allowed range.

For example, if you have a buffer of 1024b and
try to write three zero bytes into it starting at
1023 - will it be a buffer overflow? But the
buffer itself sure had room for those 3 bytes ...