Remote debugging

Debugging a program running on one system while controlling the program from another system is known as remote debugging. The debugger supports remote debugging by allowing you to run the debugger user interface on one system, while running the debug engine on another system. The system running the debugger user interface is known as the local system. The system where the debug engine runs is known as the remote system.

When debugging a program remotely, you can start the debugger in one of two ways:

In both cases, a daemon will listen for a connection. Once a connection is made you can begin to debug your program.

Why use remote debugging
You might want to use remote debugging for the following reasons:

Restriction: This information applies to remote debugging between workstation platforms only. For information for debugging an OS/390 or AS/400 program from a workstation, see the online for help for the Distributed Debugger shipped with products that support OS/390 or AS/400.

ngrelt.gif (466 bytes)
ngaix.gif (1051 bytes)ngwin.gif (1069 bytes)Starting the debugger for debugging compiled languages remotely
ngaix.gif (1051 bytes)ngwin.gif (1069 bytes)Starting the debugger for debugging interpreted Java remotely
Starting the debugger user interface daemon

ngrelr.gif (548 bytes)
Remote debugging limits