The debugger allows you to run the debugger user interface and the debug engine on separate machines. These separate machines can be running different operating systems. When you start the debugger for remote debugging, you first start a debug engine daemon. This daemon waits for a connection from the debugger user interface. Once a connection is established, you can begin to debug your program.
Debugging compiled languages remotely
To start debugging a remote program from the command line:
Tip: The debug engine is terminated if the debugger cannot load the program you want to debug. Also, the debug engine is terminated when the program you are debugging runs to completion or is terminated manually. To prevent the debug engine from being terminated in these situations, use the -qsession=multi option of the irmtdbgc command.
Debugging interpreted Java programs remotely
To start debugging a remote interpreted Java program from the command line:
Restriction:
The above method does not apply when debugging interpreted Java programs on Solaris. To
debug an interpreted Java program running on Solaris, see the related topic below.
Warning: When debugging your interpreted Java program remotely, communication between the debugger and the program being debugged may be terminated prematurely by the JVM. If this happens, you will need to reload your program. To reload your program, select File > Load Program and enter the required information in to the Load Program dialog.
Tip: The debug engine is terminated if the debugger cannot load the program you want to debug. Also, the debug engine is terminated when the program you are debugging runs to completion or is terminated manually. To prevent these situations use the -multi option of the irmtdbgj command.