Related:

• line 666 [from Christian eschatological myth] n. The notional line of source at which a program fails for obscure reaso
  implying either that somebody is out to get it (when you are the programmer), or that it richly deserves to be so gotten (when you are not)....
• 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....
• buffer overflow n. What happens when you try to stuff more data into a buffer (holding area) than it can handle.
  This problem is commonly exploited by crackers to get arbitrary commands executed by a program running with root permissions....
• comment out: vt. To surround a section of code with comment delimiters or to prefix every line in the section with a comment marke
  his prevents it from being compiled or interpreted....
• ided: /str:'d*d/ [scientific computing] adj. Said of a sequence of memory reads and writes to addresse
  each of which is separated from the last by a constant interval called the `stride length'....
• cycle: 1. n. The basic unit of computation. What every hacker wants more of (noted hacker Bill Gosper describes himself as a "cycle junkie").
  One can describe an instruction as taking so many `clock cycles'....
• bug n. An unwanted and unintended property of a program or piece of hardware, esp.
  one that causes it to malfunction. Antonym of feature....
• defenestration: [from the traditional Czechoslovakian method of assassinating prime ministers, via SF fandom] n.
  1. Proper karmic retribution for an incorrigible punster....
• miswart: /mis-wort/ [from {wart} by analogy with {misbug}] n.
  A {feature} that superficially appears to be a {wart} but has been determined to be the {Right Thing}....