Visual COBOL enables you to debug local projects while running them on a remote machine, or while your local project interacts with applications
running on a remote machine.
The following must be configured:
Remote debugging of local projects is handled by the
cobdebugremote32 process (or
cobdebugremote64 for a 64-bit process), located in
$COBDIR/bin of the remote machine.
Note: If you intend to remotely debug callable shared objects (.so), you must set the COBIDY environment variable to the location of the
.idy file before you start
You must start the process before communication can be established. This process terminates automatically when you terminate
the debug session either by disconnecting from or stopping the debugged application. You can use the following options:
- no options
- Starts the process and opens a random port for remote connections. The port number is displayed in the console.
- Specify the machine that the process is running on. Only valid with the
- Specify the port to use to listen for connection requests.
- Specify the range of ports to use. If port
nnnnn is in use, the next port is tried until a free port is found. If no free ports are found in the range, the utility returns
Note: You must enter the same number you set as the
port option in the
cobdebugremote port field of your debug configuration.
- After the debug session has been completed, start listening for another connection. If no option is specified, the process
exits after the debug session has completed.
- Causes the process that is listening on the port to exit. Must be used with the
port option. This is only valid when the process is waiting for a connection.
Tip: You need to start a
cobdebugremote process for every debug session therefore it is recommended to use the
repeat option. This ensures the process listens for another connection after the debug session has completed.