QuoteRef: sattEH5_1975 ;; Gives extensive description of debugging system (low overhead) using interrupt driven monitors

4 ;;Quote: the most effective debugging techniques are built into the program itself; produce a big gain in productivity

QuoteRef: sattEH5_1975 ;;4 assumes no part of program error-free.

QuoteRef: sattEH5_1975 ;;4 bounded amount of possible diagnostic output

4 ;;Quote: a few repetitions of loops and recursion will show errors; like mathematical induction

5 ;;Quote: traces statement 2 or more times; arguments, results, source, execution count; unexecuted instructions, procedure calls

QuoteRef: sattEH5_1975 ;;5 shows blocking on program listing by 1-start block at level 1 and -1 end block at level one very readable

QuoteRef: sattEH5_1975 ;;12 gives profile of execution counts on first statement of each block and rest of block by;

QuoteRef: sattEH5_1975 ;;13 dump of arrays shows first, last and up to six middle values

QuoteRef: sattEH5_1975 ;;13 assertion statements which force an error when false

QuoteRef: sattEH5_1975 ;;32 Hartley and Wheeler: Autotrace- traces by output whenever more statements executed between labels then before

251 ;;Quote: post mortem dump and execution profile are important parts of a programming system

251 ;;Quote: selective tracing works best for simple sequencing, explicit assignments, subtle bugs; poor for nested functions

QuoteRef: sattEH5_1975 ;;252 large programs cause difficulty for tracing cause information is buried in irrelevant data