Debugging client applications from startup

By issuing a modified command when you start your client application, you can have the Debugger attach to the client process from startup. This is useful if your application fails before reaching the server.

C++ applications:

  1. Start OLT.
  2. Do either step 3 or 4.
  3. If the Debugger daemon is on the same workstation as your client application, enter this command:
    idebug -qlang=cpp yourapp

    where:

  4. If the Debugger daemon is on a different workstation than the machine running the client application (for example, your application is running on Solaris), do the following:
    1. If the Debugger daemon has been started, go to step 4b. If the Debugger daemon has not been started, start the Debugger user interface daemon on a Windows NT/2000 or AIX workstation with this command:
      idebug -qdaemon -quiport=8001 -qquiet
    2. Start the client application with the Debugger with the command:
      irmtdbgc -qhost=<Hostname> -quiport=8001 yourapp 

      where:

      • <Hostname> is the hostname of the Windows NT/2000 or AIX workstation where you started the Debugger daemon.
      • 8001 is the port number for the Debugger daemon. This parameter can be modified if port 8001 is busy. Port 8002 cannot be used because it is reserved for the Debugger user interface.
      • yourappp is the fully qualified path name to your client application.

Java applications:
Start OLT and perform one of these steps:

Stepping from client to server:
In order to step from the client application into your server code, you should set your client breakpoints in the server stub, as shown below. For a C++ client in this example, set the breakpoint at line 251. For a Java client, set the breakpoint in the invoke statement (line 255):

ndsamp3c.gif (5136 bytes)

ngrelt.gif (466 bytes)
Distributed debugging using OLT


OLT troubleshooting
Java commands for tracing and debugging