Distributed debugging
To better understand this section, examine the sample SstPingPongLPHalt.
If the SST distributed architecture being used does not support logical processes, the normal debugger is provided. There are also facilities which support cross-system debugging in the manner of XD.
If Logical Process (LP) distributed architectures are being used, then the appropriate debugging tool is the distributed debugger. The distributed debugger allows you to follow logical process execution as it travels across remote spaces. This ability presents a debugging view much like that seen during normal single image debugging. In particular, the distributed debugger supports the following features:
•Full stack trimming: the entire distributed stack is displayed with all intervening system code trimmed out.
•Support for all step operations: step into, step over, and step to return.
•Out-of-context returns, process termination and drop-to-frame are handled correctly.
•Distributed debugging of the UI process.
All object spaces wishing to participate in distributed debugging must have the runtime support application (SstDebuggingSupport) loaded. Object spaces in which the distributed debugger UI is to be run must have the SstDebugging application loaded.
Only processes having an associated logical process can participate in distributed debugging.
The distributed debugger assumes the underlying SST system is working correctly; that is, the debugger is being used to debug application problems, not SST problems.
Last modified date: 04/20/2020