1. Select the Make debug-ready and Attach (local host only) radio button.
2. Enter the Process ID of the process on the local machine you want to debug.
To list the currently running OpenEdge processes, click the Get List button. The Select Process dialog box appears. For more information, see SelectProcess dialog box .
3. Enter a port number that you want to use for communicating with the client process, or leave the default (0), for the AVM to determine a usable port number.
4. Click OK.
If the connection is unsuccessful, the Debugger displays an alert box reporting the reason for the failure. For information on possible reasons for the failure, see the Using the proDebugConfig command section in Attachto Process dialog box .
Upon a successful connection, the Debugger displays a message showing the port number that it is using for the connection, in case you need to reconnect, for any reason. After the dialog box closes, the AVM instance gives control to the Debugger, and the listing for the currently running procedure appears in the source code pane, at the point where the Debugger connection was acknowledged. For hidden procedures, the source code pane appears empty, but the Debugger announces the connection and indicates that the AVM instance will break at the first line of application code. Debugging can proceed as described for all other modes.
For an AppServer process or WebSpeed agent, if the Debugger successfully alters the debug-ready state, it writes the status (on or off) to the log file.
