Computation histories are more commonly used in reference to Turing machines. The configuration of a single-tape Turing machine consists of the contents of the tape, the position of the read/write head on the tape, and the current state of the associated state machine; this is usually written

where
is the current state of the machine, represented in some
way that's distinguishable from the tape language, and where
is
positioned immediately before the position of the read/write head.
Consider a Turing machine
on input
. The first
configuration must be
, where
is the initial state of the Turing machine. The machine's state in the final
configuration must be either
(the accept state) or
(the reject state). A configuration
is a valid successor
to configuration
if there's a transition from the state in
to the state in
which manipulates the
tape and moves the read/write head in a way that produces the result in
.[2]
Computation histories can be used to show that certain problems for
pushdown automata are undecidable. This is because the language of
non-accepting computation histories of a Turing machine
on input
is a context-free language recognizable by a
non-deterministic pushdown automaton.
We encode a Turing computation history
as the
string
, where
is the encoding of configuration
, as discussed above, and where
every other configuration is written in reverse. Before reading a particular
configuration, the pushdown automaton makes a non-deterministic choice
to either ignore the configuration or read it completely onto the stack.
- If the pushdown automaton decides to ignore the configuration, it simply reads and discards it completely and makes the same choice for the next one.
- If it decides to process the configuration, it pushes it completely onto the stack, then verifies that the next configuration is a valid successor according to the rules of
. Since successive configurations are always written in opposite orders, this can be done by, for each tape symbol in the new configuration, popping off a symbol from the stack and checking if they're the same. Where they disagree, it must be accountable for by a valid transition of
. If, at any point, the automaton decides that the transition is invalid, it immediately enters a special accept state which ignores the rest of the input and accepts at the end.
In addition, the automaton verifies that the first configuration is the correct
initial configuration (if not, it accepts) and that the state of the final
configuration of the history is the accept state (if not, it accepts). Since
a non-deterministic automaton accepts if there's any valid way for it to accept,
the automaton described here will discover if the history is not a valid
accepting history and will accept if so, and reject if not. [3]
This same trick cannot be used to recognize accepting computation histories
with an NPDA, since non-determinism could be used to skip past a test that would
otherwise fail. A linear-bounded Turing machine is sufficient to recognize
accepting computation histories.
This result allows us to prove that
, the language
of pushdown automata which accept all input, is undecidable. Suppose
we have a decider for it,
. For any Turing machine
and input
, we can form the pushdown automaton
which accepts non-accepting computation histories for that
machine.
will accept if and only if there are no
accepting computation histories for
on
; this
would allow us to decide
, which we know to be undecidable.