Important Notice

The pages on this site contain documentation for very old MS-DOS software, purely for historical purposes. If you're looking for up-to-date documentation, particularly for programming, you should not rely on the information found here, as it will be woefully out of date.

 ◄Summary► ◄Description►                     ◄Up► ◄Contents► ◄Index► ◄Back►
────────────────────────────────────────────────────────────────────────────
 
     Use the Trace (T) command to trace into calls. To execute calls
     without tracing into them, use the Program Step (P) command
     instead. Both commands execute DOS function calls without tracing
     into them. Although CodeView cannot trace into DOS function calls
     directly, it can trace through BIOS calls in Assembly or Mixed
     mode.
     See: ◄Program Step (P) Command-Window Command►
          ◄Source Display Mode (S) Command-Window Command►
          ◄Options Menu: Source Window Command►
 
     Since the Trace command uses the hardware trace mode of the
     8086 family of processors, you can also trace instructions stored
     in read-only memory (ROM). However, the Program Step command
     does not work in ROM; in this case, it has the same effect as the
     Go (G) command.
     See: ◄Program Step (P) Command-Window Command►
          ◄Go (G) Command-Window Command►
 
     In OS/2 programs, CodeView cannot automatically trace into code
     segments or dynamic-link libraries (DLLs) defined with the
     NONCONFORMING and IOPL attributes. However, you can set a
     breakpoint on the function name, then trace into the function
     after reaching the breakpoint.
     See: ◄I/O Privilege Code Attributes (LINK)►
          ◄Conforming Code Attributes (LINK)►
                                    -♦-