Microsoft KB Archive/40584
INF: CodeView’s Internal Debugger Error Numbers PSS ID Number: Q40584 Article last modified on 10-27-1994
2.20 3.00 3.11 3.14 | 2.20 3.00 3.11 3.12 3.50
MS-DOS | OS/2
|The information in this article applies to:|
|- Microsoft CodeView for MS-DOS, versions 2.2, 3.0, 3.11, and 3.14 - Microsoft CodeView for OS/2, versions 2.2, 3.0, 3.11, 3.12, and 3.5|
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.20 3.00 3.50 CvwIss KBCategory: kbtool KBSubCategory: CvwIss
Copyright Microsoft Corporation 1994.