Summary (Dump) Tab

Similar to the Summary (Live) tab, but with several important differences. This tab is displayed only when you have loaded a dump file for examination in Source Debugger. The path to the dump file will be displayed at the top of the window.

All information in the Summary (Dump) window applies to the workstation on which the dump was created.

(For instructions to create a dump file, see: Dump Files & Forcing Communication Log Files.)

If the dump file was created on another workstation, you may not have a local copy of the source code for custom modules in that application. If that other workstation is on your network, you can direct the Source Debugger to open source code files from that computer rather than needing to copy the files to the local machine.

Differences from the System (Live) tab include:

• Operating system, VTScada license information, and the list of applications all refer to the machine where the file was created.
• The modules list will be empty as none from that workstation are loaded and running locally.
• Threads: Identifies the set of threads that were running within VTScada at the time of the dump. The number to the right of the thread name is the Windows thread identifier. The module that last ran, its state, and its statement number are identified. Under the System subheading (within the Threads section) the sequence of execution that last took place prior to the dump is provided (this is the same information as is presented in the Thread List Application - time, module name, state, and statement number).

When examining a dump file, the last statement executed can be determined from the thread list. This can be helpful to identify the cause of a crash.