ID Number: Q40584
2.x 3.00 3.10 3.11 3.14 | 2.x 3.00 3.10 3.11 3.12 3.50
MS-DOS | OS/2
Summary:
If the Microsoft CodeView debugger terminates with the message
"Internal Debugger Error," the error message text is followed by a
number. This number is rarely significant and it is unlikely that it
will help in determining the reason that CodeView exited. The value
displayed with an internal debugger error is just the value in the AX
register at the time that the error occurred.
Generally, internal debugger errors are caused by interference, such
as when terminate-and-stay-resident software in memory causes
interrupt conflicts with CodeView. However, in rare instances the
displayed value after an internal debugger error could be an errno
return value from a C run-time function. The only way to verify this
is to look up the value in ERRNO.H and check whether the number is
even in the range of errno values, and if so, whether the particular
value makes any sense in the given context. Most likely this will not
be the case and you will need to pursue the problem through other
means (such as checking memory for resident software, incompatible
device drivers, incorrect video drivers, and so on.)
Additional reference words: 2.0 2.00 2.1 2.10 2.2 2.20 2.3 2.30 2.35
3.0 3.00 3.1 3.10 3.11 3.12 3.14 3.5 3.50