Jump to content

Talk:Buffer over-read

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia

Created — To do

[edit]

I have just created this, with a redirect from buffer overread, though which spelling is better I wouldn’t know. It have included, commented out, almost all of buffer overflow, so anyone is welcome to transform that and to discard what is irrelevant. I don’t intend to do anything more, apart from adding some links from other articles, in the next few hours, maybe not even the next few days, so anyone really is welcome. PJTraill (talk) 10:26, 24 April 2014 (UTC)[reply]

Re spelling: Google gives About 43,400,000 results for over-read, About 35,600 results for overread, so the name appears appropriate. PJTraill (talk) 10:35, 24 April 2014 (UTC)[reply]

Over-read, under-read, out-of-bounds read

[edit]

Should this article mention the distinction between "over-read" and "under-read"? By MITRE's classification, these are different types of "out-of-bounds reads", distinguished by which end of the buffer the program falls off of. I don't know whether this distinction is universal. Many programmers don't think about whether "over-read" and "out-of-bounds read" are exact synonyms or not, because "under-reads" are much less common. Jruderman (talk) 08:34, 24 July 2024 (UTC)[reply]

There's a second reason that "out-of-bounds read" could be considered broader than "buffer over-read": a program could read out-of-bounds on an allocation that isn't a "buffer". I'm not sure why that would happen, but C++ programs do a lot of strange things. Jruderman (talk) 08:43, 24 July 2024 (UTC)[reply]