CodeView Unexpectedly Exits to DOS or Steps Instead of Tracing

ID Number: Q37566

1.x 2.00 2.10 2.20 2.30 2.35 3.00 3.10 3.11 3.14

MS-DOS

Summary:

When debugging a program with CodeView versions earlier than 3.0,

certain operations may cause CodeView to exit to DOS without giving

any warning or error message. Some of the operations that cause this

behavior are trying to access help, setting a watch variable, and

returning from a DOS shell.

This problem occurs because not enough file handles are being

allocated at boot time with the "files=XX" statement in the CONFIG.SYS

file. An error message is printed, but then overwritten before most

people can see it.

With CodeView version 3.0 and above, the debugger will no longer exit

to DOS; however, in certain circumstances, having the files set too

low will result in the inability to trace through some of the source

code. When this occurs, with an attempt to trace into a function in

another module, CodeView will behave as if you did a step instead (to

run past the call). CodeView will not halt execution until the next

instruction in the current file.

In either case, the solution is to make sure that files are set to 20

in CONFIG.SYS.

Additional reference words: 1.0 1.00 1.1 1.10 2.00 2.0 2.00 2.1 2.10

2.2 2.20 2.30 2.30 2.35 3.0 3.00 3.1 3.10 3.11 3.14