The term spread to MIT and CMU early and is now in general use.
Ironically, Wirth himself remained unaware of its derivation for
nearly 30 years, until GLS dug up this history in early 1993! See
{double bucky}, {quadruple bucky}.

:buffer chuck: /n./ Shorter and ruder syn. for {buffer
overflow}.

:buffer overflow: /n./ What happens when you try to stuff more
data into a buffer (holding area) than it can handle. This may be
due to a mismatch in the processing rates of the producing and
consuming processes (see {overrun} and {firehose syndrome}),
or because the buffer is simply too small to hold all the data that
must accumulate before a piece of it can be processed. For
example, in a text-processing tool that {crunch}es a line at a
time, a short line buffer can result in {lossage} as input from
a long line overflows the buffer and trashes data beyond it. Good
defensive programming would check for overflow on each character
and stop accepting data when the buffer is full up. The term is
used of and by humans in a metaphorical sense. "What time did I
agree to meet you? My buffer must have overflowed." Or "If I
answer that phone my buffer is going to overflow." See also
{spam}, {overrun screw}.

:bug: /n./ An unwanted and unintended property of a program or
piece of hardware, esp. one that causes it to malfunction.
Antonym of {feature}. Examples: "There's a bug in the editor:
it writes things out backwards." "The system crashed because of
a hardware bug." "Fred is a winner, but he has a few bugs"
(i.e., Fred is a good guy, but he has a few personality problems).