Remote Debugging (OS/2, Windows)
Remote debugging lets you debug programs running on one system, using a VisualAge C++
debugger running on another system. You can use remote debugging to debug different
applications on different systems from one machine. However, we recommend only one
connection to a remote machine at a time.
Why Use Remote Debugging
You might want to use remote debugging for the following reasons:
- The program you are debugging is running on an other user's system, and is behaving
differently on that system from your own. You can use the remote debug feature to debug
this program on the other system, from your system. The user on the remote system runs the
program and interacts with it as usual (except for delays introduced by breakpoints or
step commands). You interact with the debugger, but not with the I/O of the debuggee.
- It is easier to debug an application that uses graphics or has a GUI when you keep the
debugger user interface separate from the application's GUI. Your interaction or another
user's interaction with the application occurs on the remote system, while your
interaction with debugger occurs on the local system. This is usually the only way to
debug applications with "drag and drop" capabilities.
You can prevent lost PM messages to the debuggee. When
the debugger and the debuggee run on the same machine, the debugger must discard PM
messages to the debuggee to prevent the PM input queue from hanging.
Supported Communications Protocols and Platforms
The debugger supports the TCP/IP protocol to establish the communications link between
the debugger and a debuggee program running on different machines.
Limitations of Remote Debugging
Both the remote machine and the local machine must be running the same operating system
for a connection to be established. For example, both the remote machine and the local
machine must both be running OS/2.
You can establish a connection from a local machine
running Windows NT if the remote machine is running either Windows 95 or Windows NT.
Attempting to use remote debugging with the same OS/2
machine acting as both the remote and local system may cause the machine to lock up.

Communication Types

Prepare a Connection for
Remote Debugging