About the Book
Please note that the content of this book primarily consists of articles available from Wikipedia or other free sources online. Pages: 60. Chapters: 2012 RBS computer system problems, Buffer overflow, Buffer overflow protection, Bug compatibility, Bush hid the facts, Cluster (spacecraft), Computer bug, Cupertino effect, C Traps and Pitfalls, Dangling pointer, Deadlock, Fandango on core, Fragile binary interface problem, Glitch, Glitching, Glitch art, Handle leak, Heisenbug, Infinite loop, Input kludge, Integer overflow, Internet Explorer box model bug, Lapsed listener problem, List of software bugs, Locks-and-keys, Memory corruption, Memory leak, Memory safety, MissingNo., Negative cache, Off-by-one error, Priority inversion, Racetrack problem, Race condition, RFPolicy, Security bug, Software regression, Sorcerer's Apprentice Syndrome, Stack buffer overflow, Stack overflow, Stale pointer bug, Therac-25, The Daily WTF, Time formatting and storage bugs, Undefined variable, Uninitialized variable, Y1C Problem, Year 2000 problem. Excerpt: The Year 2000 problem (also known as the Y2K problem, the Millennium bug, the Y2K bug, or simply Y2K) was a problem for both digital (computer-related) and non-digital documentation and data storage situations which resulted from the practice of abbreviating a four-digit year to two digits. In 1997, The British Standards Institute (BSI) developed a standard, DISC PD2000-1, which defines "Year 2000 Conformity requirements" as four rules: It identifies two problems that may exist in many computer programs. Firstly, the practice of representing the year with two digits becomes problematic with logical error(s) arising upon "rollover" from x99 to x00. This has caused some date-related processing to operate incorrectly for dates and times on and after 1 January 2000, and on other critical dates which were billed "event horizons." Without corrective action, long-working systems would break down when the ..".97, 98, 99, 00..." ascending...
