can't find the saved registers for the CALL command for frame frame-
 addr

    Facility: DEBUG, VMS Debugger

    Explanation: The debugger is attempting to chain down the call
    stack, following frame pointers. The debugger has determined
    that the frame at frame-addr was caused by a CALL command from
    the debugger. The debugger is unable to find the register set it
    saved for the context before the CALL command.

    User Action: Determine what part of your code is writing into the
    FP register or overwriting the saved frame pointer on the call
    stack (or a preceding saved frame pointer) and correct it. Since
    the debugger looks at the call stack to symbolize addresses, you
    may suppress some of these messages by typing the command "SET
    MODE NOSYMBOLIC".