Difference between revisions of "Single-step"
From Computer History Wiki
(Pretty stubby, but a start...) |
m (better) |
||
(One intermediate revision by the same user not shown) | |||
Line 1: | Line 1: | ||
− | To '''single-step''' a program is to have it [[execute]] a single [[instruction]], and then [[halt]], so that the [[programmer]] can see what the program is doing. | + | To '''single-step''' a [[program]] is to have it [[execute]] a single [[instruction]], and then [[halt]], so that the [[programmer]] can see what the program is doing. |
There are a number of different ways to cause single-stepping: on older computers with [[front panel]]s, there is usually a switch setting which allows single-stepping the [[Central Processing Unit|CPU]]. On newer machines, there is usually some way to cause the CPU to execute a single instruction, and then [[trap]]; [[debugger]] [[software]] then takes control, and allows the same sort of examination. | There are a number of different ways to cause single-stepping: on older computers with [[front panel]]s, there is usually a switch setting which allows single-stepping the [[Central Processing Unit|CPU]]. On newer machines, there is usually some way to cause the CPU to execute a single instruction, and then [[trap]]; [[debugger]] [[software]] then takes control, and allows the same sort of examination. | ||
{{semi-stub}} | {{semi-stub}} | ||
+ | |||
+ | [[Category: CPU Basics]] |
Latest revision as of 15:15, 15 December 2018
To single-step a program is to have it execute a single instruction, and then halt, so that the programmer can see what the program is doing.
There are a number of different ways to cause single-stepping: on older computers with front panels, there is usually a switch setting which allows single-stepping the CPU. On newer machines, there is usually some way to cause the CPU to execute a single instruction, and then trap; debugger software then takes control, and allows the same sort of examination.