Change of Radix Does Not Change Array Index

Last reviewed: July 17, 1997
Article ID: Q26972
2.20 3.00 3.11 3.14 4.00 4.01 4.05 | 2.20 3.00 3.11 3.12 3.50 | 3.x 4.0x
MS-DOS                             | OS/2                     | WINDOWS
kbtool

The information in this article applies to:

  • Microsoft CodeView for MS-DOS, versions 2.2, 3.0, 3.11, 3.14, 4.0, 4.01, and 4.05
  • Microsoft CodeView for OS/2, versions 2.2, 3.0, 3.11, 3.12, and 3.5
  • Microsoft CodeView for Windows, versions 3.0, 3.05, 3.06, 3.07, 4.0, and 4.01

The Microsoft CodeView debugger assumes all array indexes are in the current radix. Therefore, if a watch is placed on a particular array element and the radix is then changed, the value displayed in the Watch window may change.

To illustrate, assume the current radix is 10 and the program being debugged contains an array called buffer. If a watch has been placed on buffer[10] and the radix is then changed to base 16, the Watch window will still show buffer[10], but the 10 now refers to 0x10 or decimal 16. Thus, the value displayed is buffer[16].

This behavior occurs because CodeView reinterprets the items in the Watch window each time; when you set a watch on a variable, CodeView does not "compile" that address into some internal memory location. Instead, it recalculates the watch statement each time.

This behavior was changed in CodeView version 4.1.


Additional reference words: kbinf 2.20 3.00 3.50 4.00
KBCategory: kbtool
KBSubcategory: CvwIss
Keywords : kb16bitonly


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: July 17, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.