Depending on the programming language and platform of the program you are debugging, select the appropriate tab for a description of the controls and control groups. The tabs cover the following categories of programming languages on various platforms:
The controls and control groups are described on separate tabs for each category of programming language on various platforms. Select the appropriate tab from the following:
Use the Attach dialog box to select and attach to a process or JVM that is already running so it can be debugged.
This tab is used for attaching to compiled language processes running on AIX, Solaris, and Windows. Attaching to an operating system process or to any of the processes of the Debugger itself can cause unpredictable results and should therefore not be done.
Terminating a process for programs written in compiled languages has additional considerations. The following are notes describing how the Debugger handles attached processes on exit.
Controls and control groupings are described below. Group and subgroup names appear in italics, and control names appear in bold.
Select local or remote execution of the program | Select one of the following options to define the location in which the
process being attached to will be running.
|
||||||||
Specify the dominant language the Debugger will use | Select the appropriate programming language from this drop-down list. The default value is C++. | ||||||||
Process path (optional) | Enter the process path, if known.
The operating system can determine the process path from the process ID and does not require you to specify this information. Select the radio button for the method to be used to specifiy the process ID.
|
||||||||
Use program profile | Check this box if you want to use the breakpoint, monitor,
and Application Preferences settings that were associated with your program
during your last Debugger session. If you are
debugging your program for the first time, the Debugger uses the default
Application Preferences settings, with no initially set breakpoints. Checking this box will also associate and save any changes you make to the monitors and breakpoints with your program when you end your Debugger session. Note: If you add or delete lines in your source file, recompile it, and then debug the program again with a saved program profile, line breakpoints may no longer match the code they were initially set for because line breakpoint information is saved by line number, not by the content of the line. |
The push buttons of the Attach dialog box are described in the following table. Control names appear in bold.
Push buttons |
|
Use the Attach dialog box to select and attach to a process or JVM that is already running so it can be debugged.
Restriction: This tab applies to interpreted Java programs only. It does not apply to debugging High Performance Compiled Java programs or OS/390 Java program objects.
Use the Interpreted tab to attach to an already running Java Virtual Machine (JVM). Attaching to a running JVM allows you to debug the interpreted Java program running inside the JVM. When attaching to a JVM, you select the location of execution for the debug engine rather than the location of execution for the program.
Controls and control groupings are described below. Group and subgroup names appear in italics, and control names appear in bold.
Select a method to attach to the JVM |
|
||||||||||||
Use program profile | Check this box if you want to use the breakpoint, monitor,
and Application Preferences settings that were associated with your program
during your last Debugger session. If you are
debugging your program for the first time, the Debugger uses the default
Application Preferences settings, with no initially set breakpoints. Checking this box will also associate and save any changes you make to the monitors and breakpoints with your program when you end your Debugger session. Note: If you add or delete lines in your source file, recompile it, and then debug the program again with a saved program profile, line breakpoints may no longer match the code they were initially set for because line breakpoint information is saved by line number, not by the content of the line. |
The push buttons of the Attach dialog box are described in the following table. Control names appear in bold.
Push buttons |
|
![]() |
Use the Attach dialog box to attach to an existing
job on an AS/400. Jobs on the AS/400 can be one of the following:
All types of jobs can be attached to by the Debugger. When you are attaching to an existing AS/400 job, the behavior of the debug session changes depending on whether or not you select Step Into in this dialog box. For more details, see the description of the Step Into box in this group. Controls and control groups in this group are used as follows:
|
The push buttons of the Attach dialog box are described in the following table. Control names appear in bold.
Push buttons |
|