Technical data

Programming Release Notes
6.9 Debugger
6.9.5 Enumeration Literals as Class Members
V7.3
Previous versions of the debugger did not treat C++ enumeration literals as class
members. This problem has been corrected. For example, given the following
declaration, the debugger will match ’B::red’ and ’b.red’, and ’p->red’:
struct B { enum colors { yellow, red, green, purple }; } b, *p;
6.9.6 Global Symbol Table Search
V7.3
When debugging C and C++ programs, previous versions of the debugger had a
problem when searching the global symbol table, which was caused by incorrect
internal assumptions about case. For example:
DBG> EXAMINE FOO
%DEBUG-E-NOSYMBOL, symbol ’foo’ is not in the symbol table
DBG> EXAMINE FOO
X_CXXC_BUGS3560A\foo: 0
This problem has been corrected.
6.9.7 Global Section Watchpoints (Alpha Only)
V7.3
Previous versions of the debugger sometimes had difficulty setting watchpoints
on global section variables. This problem has been corrected.
6.9.8 Array Elements Displayed Differently on VAX and Alpha
V7.3
Previous versions of the Alpha debugger displayed FORTRAN arrays in row-
major order. This problem has been corrected so that the Alpha debugger now
displays FORTRAN arrays in column-major order.
6.9.9 Wrong Address in C++
V7.3
While debugging a C++ program, previous versions of the debugger sometimes
have trouble accessing an object. For example:
DBG> EXAMINE C
%DEBUG-E-NOACCESSR, no read access to address 000000017AEF3A34
The debugger would sometimes look for a 64-bit address when it should have
been looking for a 32-bit address. This problem has been corrected.
6.9.10 Cross-Image Symbol Fixup
V7.3
When using the Version 7.2 Alpha debugger, attempts to examine or evaluate
universal data variables sometimes resolved to the wrong address because of a
cross-image symbol fixup problem. This problem has been corrected.
6–10 Programming Release Notes