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.
To debug the client from startup, complete the steps under the topic "Running the debugger from OLT", but substitute one of the following commands to start your client application:
C++ applications:
If the debugger daemon has been started on the same workstation as your
client application, enter this command:
idebug -qlang=cpp yourapp
If you started the debugger daemon on a different workstation or if your application is running on Solaris, follow these step:
where:
Java applications:
At a command prompt, enter this command:
for Java 1.1.x:
idebug -qlang=java -qhost=<Hostname>
-qjvmargs="-nojit
-Dcom.ibm.CORBA.EnableApplicationOLT=true
-Dcom.ibm.CORBA.requestTimeout=0
-Dcom.ibm.CORBA.BootstrapHost=<BootstrapHostname>
-Dcom.ibm.CORBA.OLTApplicationHost=<OLT_Server_Host>
-Dcom.ibm.CORBA.OLTApplicationPort=<OLT_Server_Port>
-DOLTClient=true
-classpath
<path\YourAppJarFile>;<path\somojor.zip>;<path\dertrjrt.jar>;%CLASSPATH%"
yourapp
for the Java 2 platform:
idebug -qlang=java -qhost=<Hostname>
-qjvmargs="-Djava.compiler=NONE
-Dcom.ibm.CORBA.EnableApplicationOLT=true
-Dcom.ibm.CORBA.requestTimeout=0
-Dcom.ibm.CORBA.BootstrapHost=<BootstrapHostname>
-Dcom.ibm.CORBA.OLTApplicationHost=<OLT_Server_Host>
-Dcom.ibm.CORBA.OLTApplicationPort=<OLT_Server_Port>
-DOLTClient=true
-Xbootclasspath:<path\YourAppJarFile>;<path\somojor.zip>;<path\dertrjrt.jar>;%JAVA_HOME%\lib\tools.jar;%JAVA_HOME%\jre\lib\rt.jar;%CLASSPATH%
yourapp
where:
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):