Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "PTP/designs/debugger launch"
(New page: == Debugger Launch Process == When the user hits the debug button, debug launch proceeds as follows: 1. The debugger is initialized. The following steps are performed: a. Compute the deb...) |
(→Debugger Launch Process) |
||
Line 3: | Line 3: | ||
When the user hits the debug button, debug launch proceeds as follows: | When the user hits the debug button, debug launch proceeds as follows: | ||
− | + | # The debugger is initialized. The following steps are performed: | |
− | + | ## Compute the debugger arguments and save in the DEBUGGER_ARGS launch attribute | |
− | + | ## Verify that the debugger executable (as specified in the Debugger tab) exists on the target machine | |
− | + | # The job is submitted with mode set to "debug". The command submitted is assumed to launch the debugger executable and supply the debugger arguments. | |
− | + | # If the RM has specified "needsDebuggerLaunchHelp" AND the job state changes to RUNNING, the following steps are performed: | |
− | + | ## A routing file is created that contains the tuples (index, host, port) for each process. The host information is obtained from the IPJob#getProcessNodeId() method (the other values are computed). The routing file is assumed to be in a location that is accessible to all sdm processes. | |
− | + | ## The sdm master process is launched on the target machine using an IRemoteProcessBuilder. | |
− | + | ||
− | + |
Revision as of 13:16, 21 July 2011
Debugger Launch Process
When the user hits the debug button, debug launch proceeds as follows:
- The debugger is initialized. The following steps are performed:
- Compute the debugger arguments and save in the DEBUGGER_ARGS launch attribute
- Verify that the debugger executable (as specified in the Debugger tab) exists on the target machine
- The job is submitted with mode set to "debug". The command submitted is assumed to launch the debugger executable and supply the debugger arguments.
- If the RM has specified "needsDebuggerLaunchHelp" AND the job state changes to RUNNING, the following steps are performed:
- A routing file is created that contains the tuples (index, host, port) for each process. The host information is obtained from the IPJob#getProcessNodeId() method (the other values are computed). The routing file is assumed to be in a location that is accessible to all sdm processes.
- The sdm master process is launched on the target machine using an IRemoteProcessBuilder.