Debugging by thinking pdf

Debugging by thinking pdf is the process of finding and resolving defects or problems within the program that prevent correct operation of computer software or a system. Debugging tactics can involve interactive debugging, control flow analysis, unit testing, integration testing, log file analysis, monitoring at the application or system level, memory dumps, and profiling.

The terms “bug” and “debugging” are popularly attributed to Admiral Grace Hopper in the 1940s. While she was working on a Mark II computer at Harvard University, her associates discovered a moth stuck in a relay and thereby impeding operation, whereupon she remarked that they were “debugging” the system. Similarly, the term “debugging” seems to have been used as a term in aeronautics before entering the world of computers. Indeed, in an interview Grace Hopper remarked that she was not coining the term.

The moth fit the already existing terminology, so it was saved. Ernest Lawrence at UC Berkeley, dated October 27, 1944, regarding the recruitment of additional technical staff. The Oxford English Dictionary entry for “debug” quotes the term “debugging” used in reference to airplane engine testing in a 1945 article in the Journal of the Royal Aeronautical Society.

Hopper’s bug was found on September 9, 1947. The term was not adopted by computer programmers until the early 1950s. The seminal article by Gill in 1951 is the earliest in-depth discussion of programming errors, but it does not use the term “bug” or “debugging”. In the ACM’s digital library, the term “debugging” is first used in three papers from 1952 ACM National Meetings.

Two of the three use the term in quotation marks. By 1963 “debugging” was a common enough term to be mentioned in passing without explanation on page 1 of the CTSS manual.

scroll to top