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:

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.



ngos2.gif (402 bytes) ngwin.gif (1069 bytes)Communication Types


ngos2.gif (402 bytes) ngwin.gif (1069 bytes)Prepare a Connection for Remote Debugging