◄Up► ◄Contents► ◄Index► ◄Back►
────────────────────────────────────────────────────────────────────────────
 
     A "debug history" is a record of a debugging session.
 
     Debug history acts like a tape recorder that records
 
        ■ A debug command tape containing all the commands you give the
          debugger. This is the file <PROGRAM>.CVH.
 
        ■ A user input tape containing all program input typed at the
          keyboard. This is the file <PROGRAM>.CVI.
 
     For <PROGRAM>, CodeView uses the base name of the executable file
     you are debugging.
 
     Once you have recorded debug commands and user input, you can
 
        ■ Undo debugging commands by choosing the Undo command from
          the Run menu
 
        ■ Move back and forth through the session using SHIFT+F8 and
          SHIFT+F10, respectively
 
        ■ Use the Replay command on the Options menu to tell CodeView
          whether to replay debug commands or user input, or both
 
        ■ Choose the Replay command from the Run menu to replay
          commands or user input entered
 
     In protected-mode programs, debug history has the following
     restrictions:
 
        ■ In multiprocess programs, only the debug command tape can be
          used.
 
        ■ Debug history does not work in multithread programs or
          programs with asynchronous actions.
 
     Use debug history to
 
        ■ Recreate the circumstances that led to an error
 
        ■ Save your work from one debug session to another
 
        ■ Locate problems in the logic of your programs
 
        ■ Keep a regression test to verify a particular program's
          behavior
 
     See: ◄Run Menu: Restart Command►
          ◄Run Menu: Replay Command►
          ◄Run Menu: Undo Command►
          ◄Options Menu: Replay Command►
                                    -♦-