Opens a system dump for analysis by the System Dump Debugger (kept debugger only). Format ANALYZE/CRASH_DUMP
1 – Description
For OpenVMS Integrity servers and Alpha systems, invokes the System Dump Debugger (SDD) to analyze a system dump. SDD is similar in concept to the System Code Debugger (SCD). While SCD allows connection to a running system, with control of the system's execution and the examination and modification of variables, SDD allows analysis of memory as recorded in a system dump. Use of SDD usually involves two systems, although all of the required environment can be set up on a single system. The description that follows assumes that two systems are being used: o The build system, where the image that causes the system crash has been built o The test system, where the image is executed and the system crash occurs In common with SCD, the OpenVMS debugger user interface allows you to specify variable names, routine names, and so on, precisely as they appear in your source code. Also, SDD can display the source code where the software was executing at the time of the system crash. SDD recognizes the syntax, data typing, operators, expressions, scoping rules, and other constructs of a given language. If your code or driver is written in more than one language, you can change the debugging context from one language to another during a debugging session. To use SDD you must do the following: o Build the system image or device driver that is causing the system crash. o Boot a system, including the system image or device driver, and perform the necessary steps to cause the system crash. o Reboot the system and save the dump file. o Invoke SDD, which is integrated with the OpenVMS debugger. For more information about using the SDD, including a sample SDD session, see the VSI OpenVMS System Analysis Tools Manual. Related commands: ANALYZE/PROCESS_DUMP CONNECT %NODE SDA
2 – Example
DBG> ANALYZE/CRASH_DUMP DBG> Invokes SDD from within the kept debugger.