1.DBG> SHOW CALLS
       module name routine name  line     rel PC           abs PC
      *MAIN         FFFF          31  00000000000002B8 00000000000203C4
      -the above appears to be a null frame
                                     in the same scope as the frame below
      *MAIN         MAIN          13  00000000000000A8 00000000000200A8
                                      0000000000000000 FFFFFFFF8255A1F8

      This example has been reformatted for Help, and may appear
      slightly different from the actual output display. This example
      is on an Alpha system. Note that sections of routine prologues
      and epilogues appear to the debugger to be null frames. The
      portion of the prologue before the change in the frame pointer
      (FP) and the portion of the epilogue after restoration of the
      FP each look like a null frame, and are reported accordingly.

    2.DBG> SHOW CALLS

       module name    routine name     line           rel PC           abs PC
      *MAIN           FFFF               18       0000000000000190 0000000000010190
      *MAIN           MAIN               14       0000000000000180 0000000000010180
                                                  FFFFFFFF80C2A200 FFFFFFFF80C2A200

      This example has been reformatted for Help, and may appear
      slightly different from the actual output display. This example
      is on Integrity servers. Note that Integrity server prologues
      do not appear to be null frames to the debugger.