Debugging is a methodical process of finding and reducing the number of bugs, or defects, in a computer program or a piece of electronic hardware thus making it behave as expected. Debugging tends to be harder when various subsystems are tightly coupled, as changes in one may cause bugs to emerge in another.

Origin

---

There is some controversy over who first used the term "debug" (see the Computer bug article for a full discussion). Some claim that the term "debugging" was first used by Glenford J Myers in his 1976 book Software Reliability: Principles and Practices where he defined it as "diagnosing the precise nature of a known error and then correcting the error", while others claim it was associated with Admiral Grace Hopper in the 1940s.

The story goes that when one of the early computers that Hopper was working with malfunctioned, it was discovered that a moth had gotten into a relay (they were used for the logic of computers at that time), changing the logic of the program. This was the origin of the term bug in reference to problems with computer programs running correctly. Some believe that the staff then started using the term debugging to describe the process of removing errors from computer programs.

More on [ Debugging ]

Checking and Debugging - Twitter Search

If I'm not mistaken it looks like one could use google wave as a cooperative code writing tool with debugging and syntax checking.
marshaleaton (Marshal Eaton) Wed, 02 Dec 2009 00:48:41 -0000
If I'm not mistaken it looks like one could use google wave as a cooperative code writing tool with debugging and syntax checking.

Subscribe to Checking_and_Debugging RSS feed