1.DBG> EVALUATE/ADDRESS RTN-NAME

      On Integrity server systems, instead of displaying the address
      of the official function descriptor, the debugger just displays
      the code address. For example, on Alpha systems, you can enter
      the following command and then set a breakpoint when a variable
      contains the address, FOO:

    2.DBG> SET BREAK .PC WHEN (.SOME_VARIABLE EQLA FOO)

      The breakpoint occurs when the variable contains the address
      of the procedure descriptor. However, when you enter the same
      command on Integrity server systems, the breakpoint is never
      reached because, although the user variable might contain the
      address of the function descriptor for FOO, the "EQLA FOO" in
      the WHEN clause compares it to the code address for FOO. As
      a result, the user variable never contains the code address
      of FOO. However, the first quadword of an Integrity server
      function descriptor contains the code address, you can write it
      as:

    3.DBG> SET BREAK .PC WHEN (..SOME_VARIABLE EQLA FOO)

                                   NOTE

       On Integrity server systems, you cannot copy the following
       line from your BLISS code: IF .SOME_VARIABLE EQLA FOO THEN
       do-something;

    4.     DBG> EVALUATE/ADDRESS MODNAME\%LINE 110
      3942
      DBG>

      This command displays the memory address denoted by the address
      expression MODNAME\%LINE 110.

    5.DBG> EVALUATE/ADDRESS/HEX A,B,C
      000004A4
      000004AC
      000004A0
      DBG>

      This command displays the memory addresses denoted by the
      address expressions A, B, and C in hexadecimal radix.

    6.DBG> EVALUATE/ADDRESS X
      MOD3\%R1
      DBG>

      This command indicates that variable X is associated with
      register R1. X is a nonstatic (register) variable.