Dynamic Debugging Technique
debugger programs originally developed for DEC hardware; the name is a pun on the insecticide (i.e. bug-killer) DDT
Dynamic Debugging Technique (DDT) is a series of debugger programs originally developed for Digital Equipment Corporation (DEC) hardware, initially known as DEC Debugging Tape because it was distributed on paper tape. The name is a pun on the insecticide DDT, which "kills bugs".
The first version of DDT was developed at MIT for the PDP-1 computer in 1961. It was an adaptation of the early interactive, symbolic debugger FLIT (the "Flexowriter Interrogation Tape", itself a play on the name of a once-popular brand of insect spray), developed for MIT's TX-0 computer in 1959. Newer versions of DDT on newer platforms continued to use the acronym DDT, but the name "Dynamic Debugging Technique", introduced by 1965, prevailed by the late 1960s. Early versions of Digital Research's CP/M and CP/M-86 kept the name DDT (and DDT-86 and DDT-68K) for their debugger, reinterpreted as Dynamic Debugging Tool. The CP/M DDT was later superseded by the Symbolic Instruction Debugger (SID, ZSID, SID86, and GEMSID) in DR DOS and GEM.
In addition to its normal function as a debugger, DDT was also used as a top-level command shell for the Massachusetts Institute of Technology (MIT) Incompatible Timesharing System (ITS) operating system; on some more recent ITS systems, "PWORD"—which implements a restricted subset of DDT's functionality—is run first and is overlaid with DDT as soon as the user logs in. DDT could run and debug up to eight processes (called "jobs" on ITS) at a time, such as several sessions of TECO, and DDT could be run recursively - that is, some or all of those jobs could themselves be DDTs (which could then run another eight jobs, and so on). These eight jobs were all given unique names, and the usual name for the original and top-most DDT was "HACTRN" ("hack-tran"). Guy L. Steele wrote a filk poem parody of Edgar Allan Poe's "The Raven," entitled The HACTRN.
DEC-10/DEC-20 DDT
DDT (Dynamic Debugging Technique), as implemented on the DECsystem-10 & DECSYSTEM-20 allowed references to symbols within the programming being debugged.
“Dynamic Debugging Technique” enters the record as debugger programs originally developed for DEC hardware; the name is a pun on the insecticide (i.e. bug-killer) DDT. Crown Archives preserves that source wording while asking what Dynamic, Debugging and Technique can confirm, complicate or overturn.
Why this record matters
“Dynamic Debugging Technique” is worth following because a concise public description often conceals a longer documentary argument. Here, Dynamic, Debugging and Technique provides the most credible route into that argument.
The citation trail is more important than the brevity of the summary: it shows where individual claims can be examined in context. The source revision retrieved here is dated Jul 24, 2026. The linked authority identifier is Q5318964. None of the 1 selected statements returned an explicit reference. The first chronological checks are 1961, 1959 and 1965.
Overview language is designed for orientation and should not be treated as a substitute for the evidence cited beneath it. The lead is largely declarative, so disagreement and counter-evidence require a deliberate search beyond the opening account. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.
How to read it
Use the entry as an orientation point, then follow its citations and revision history. Names, dates and institutional relationships should be checked against the original record.
- Subject orientation
- Search vocabulary
- Locating named sources
The closest primary source, responsible institution and strongest cited specialist reference.
Three-step research path
- Establish the record: confirm the title “Dynamic Debugging Technique”, its source revision and the description used here.
- Expand the search: follow Dynamic Debugging Technique primary sources, Dynamic Debugging Technique archive and Dynamic research across catalogues and specialist indexes.
- Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.
Questions for further research
- Which source most directly establishes the central claim about “Dynamic Debugging Technique”?
- What terminology or title could unlock a more precise catalogue search?
- Which institution is responsible for the underlying evidence?
Search terms from this dossier
This entry incorporates text from “Dynamic Debugging Technique” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.