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.
Debugging in Protected Mode: Restrictions
◄Up► ◄Contents► ◄Index► ◄Back►
────────────────────────────────────────────────────────────────────────────
CVP.EXE, the protected-mode version of CodeView, has the following
restrictions:
■ If you want to switch between the CodeView screen and the
output screen of the program you are debugging, you must
use CodeView's F4 key or Screen Exchange (\)
command. You cannot use the OS/2 Task Manager.
See: ◄Screen Exchange (\) Command-Window Command►
■ You cannot debug asynchronously. That is, you cannot execute
the program you are debugging in one screen group and perform
other CodeView operations in a second screen group.
■ To debug a bound program in OS/2 running in the DOS session,
you must link the program with the OS2.LIB library.
■ To terminate the program you are debugging, you must type
CTRL+BREAK or ALT+SYSREQ. CTRL+C does not stop the program.
NOTE: CTRL+C may be used to pass a "break" signal to a
handler in the program.
■ Breakpoints in parts of the program that handle messages are
likely to cause deadlock conditions.
■ In a multithread program, a thread may not stop at a
breakpoint if all threads are in a critical section of
Presentation Manager code.
-♦-