HELPLIB.HLB  —  ANALYZE  /PROCESS_DUMP, Qualifiers

1    /FULL

    On VAX and Alpha systems, displays all known information about the
    failing process.

2    /IMAGE

       /IMAGE=image-name
       /NOIMAGE

    On VAX systems, specifies the image to be activated to set up the
    process context for the analysis. If you use the /NOIMAGE qualifier,
    the DELTA debugger will be used for the analysis.

    By default, symbols are taken from the image with the same name as
    the image that was running at the time of the dump.

3    /IMAGE_PATH

      /IMAGE_PATH[=directory-spec] dump-file
      /NOIMAGE_PATH

    On Alpha systems, specifies the search path the debugger is to use
    to find the debugger symbol table (DST) file.  As in prior debuggers,
    the debugger builds an image list from the saved process image list.
    When you set an image (the main image is automatically set), the
    debugger attempts to open that image in order to find the DST file.

    If you include the /IMAGE_PATH=directory-spec qualifier, the
    debugger searches for the DST file in the specified directory.
    The debugger first tries to translate directory-spec as the logical
    name of a directory search list.  If that fails, the debugger
    interprets directory-spec as a directory specification, and searches
    that directory for matching .DSF or .EXE files.  A .DSF file takes
    precedence over an .EXE file.  The name of the .DSF or .EXE file
    must match the image.

    If you do not include the /IMAGE_PATH=directory-spec qualifier,
    the debugger looks for the DST file first in the directory that
    contains the dump file.  If that fails, the debugger searches
    directory SYS$SHARE and then directory SYS$MESSAGE.  If the debugger
    fails to find a DST file for an image, the symbolic information
    available to the debugger is limited to global and universal symbol
    names.

    Version 7.3 and later debuggers check for dumpfile image specification
    and DST file link date-time mismatches and issue a warning if one is
    discovered.

    The dump-file parameter is the name of the process dump file to
    be analyzed.  Note that the process dump file file type must be .DMP
    and the DST file type must be either .DSF or .EXE.

                             Restrictions

        You cannot use a logical to redirect the search for an image
        and use the /IMAGE_PATH qualifier at the same time.  If you
        use the /IMAGE_PATH qualifier, then all images that are not
        in their original locations must be found through that path.
        Individual image logicals (for example, the "SH" in "DEFINE
        SH SYS$LOGIN:SH.EXE") are not processed.

        Additionally, you cannot input a directory search path
        directly to the /IMAGE_PATH qualifier, as it does not
        process a directory list separated by commas; however, you
        can specify a logical that translates into a directory
        search path.

4    /INTERACTIVE

       /INTERACTIVE
       /NOINTERACTIVE (default)

    On VAX systems, causes the display of information to pause when your
    terminal screen is filled. Press Return to display additional
    information.  By default, the display is continuous.

5    /MISCELLANEOUS

    On VAX systems, displays process information and registers at the
    time of the dump.  Refer to the $GETJPI system service for further
    explanation of the process information displayed.

6    /RELOCATION

    On VAX systems, displays the addresses to which data structures saved
    in the dump are mapped in P0 space. (Examples of such data structures
    are the stacks.) The data structures in the dump must be mapped into P0
    space so that the debugger can use those data structures in P1 space.
Close Help