Content deleted Content added
fr |
No edit summary |
||
Line 4:
:In 1946, when Hopper was released from active duty, she joined the Harvard Faculty at the Computation Laboratory where she continued her work on the Mark II and Mark III. She traced an error in the Mark II to a moth trapped in a relay, coining the term bug. This bug was carefully removed and taped to the log book. Stemming from the first bug, today we call errors or glitch's in a program a bug. [http://ei.cs.vt.edu/~history/Hopper.Danis.html]
Despite the colourfulnes of the above anecdote, it is known that the use of the word "bug" to describe defects in mechanical systems dates back to at least the 1870's. Thomas Edison, for one, used the word in his notebooks.
There are bugs in all useful computer programs. However, well-written programs contain relatively few bugs, and these bugs typically do not prevent the program from performing its task. In contrast, "buggy" programs contain many bugs and/or bugs which interfere with the program's functionality.▼
▲
Bugs have widely-varying effects. Some bugs have only a subtle effect on the program's functionality, and may thus lie undetected for a long time. More severe bugs may cause the program to [[crash]] or [[freeze (computing)|freeze]]. In some [[operating system|operating systems]], such as [[Microsoft Windows]], crashing or freezing programs may render the computer unusable until it is [[boot (computing)|rebooted]] (see [[blue screen of death]].) Other bugs lead to security vulnerabilities; untrapped buffer overflow is one common type of bug that often allows an attacker to execute a new program on the target machine with elevated privileges.
| |||