jdbug command

ngsol.gif (418 bytes)ngjava.gif (225 bytes)Restriction:  This is supported for Java on Solaris only.

Requirement: You must have the debug engine installed on the system in order to use this command. Check the install documentation for instructions on how to install the debug engine.

The jdbug command starts the Java debug engine. Once started, the debug engine waits to connect to the debugger user interface on the local system. You can use the debugger startup dialog on the local system or use the idebug command with the remote debug parameters to start the debugger interface on the local system.

The jdbug command has the following syntax:

jdbug [jdbug_options] [JVM_attach_parameters] [engine_daemon_parameters |ui_daemon_parameters [class_name [class_parameters]]]

where jdbug_options are zero or more of the following:

  Parameter Description
-help Displays help for the jdbug command.
-qquiet Suppresses console output.

 

Use the jvm_attach_parameters if you want to attach the debugger to a running Java Virtual Machine (JVM). You can attach to a JVM if you are starting a debug engine daemon or connecting to a debugger user interface daemon. The jvm_attach_parameters are:

  Parameter Description
-password=
<agent_password>
Specifies the agent password.

This password is printed when you start your java program using the java_g -debug command.

This parameter is required when attaching to a running JVM.

-host=
<JVM_host>
Specifies the name or address of the machine where the JVM is running.

If the JVM is running on the same machine where the debug engine will run, use "localhost".

 

Use the -qport parameter and zero or more of the other engine_daemon_ parameters if you want to start the debug engine as a daemon on the remote system. The debug engine daemon listens on a port number for a connection from the debugger user interface. Once a connection is made, you can begin debugging your program from the local system. The engine_daemon_parameters are:

  Parameter Description
-multi This option enables multiple session debugging. If this option is omitted, only single session debugging is enabled.

In single session debugging, the debug engine terminates when the program you are debugging runs to completion or is terminated manually.

In multiple session debugging, the debug engine re-initializes itself and waits for a new connection when the program you are deubugging runs to completion or is terminated manually. The debug engine must be terminated manually on the remote system.

-jvmargs=
<jvm_arguments>
Specifies arguments passed to the JVM that will run the program you want to debug. If you specify more than one option, eclose the list of options in quotation marks.

Attention: Using unsupported arguments will cause the debugger to exit. For a list of supported JVM arguments, see the related topic below.

-qport=<port> Specifies the TCP/IP port where the debug engine daemon will listen for the user interface. The default port is 8000.

If you do not use the default port, specify the same port number you use here in the -qport parameter of the idebug command.

ngaix.gif (1051 bytes) On AIX, the -qport parameter must be used to avoid conflict with other users.

 

Use the ui_daemon_ parameters if you have started the debugger user interface as a daemon. As daemon, the debugger user interface listens on a port for a debugger engine connection. Upon connecting, the debugger user interface starts and you can begin debugging your program. The ui_daemon_parameters are:

  Parameter Description
-qhost=<ui_daemon_host> Specifies the IP address or name of the machine where the user interface daemon is running.

This parameter is required when connecting to a debugger user interface daemon.

-qtitle=<ui_daemon_title> Specifies the title that will appear on the process tab
-quiport=<ui_daemon_port> Specifies the TCP/IP port used for the connection. The default port is 8001.

If you do not use the default port, specify the same port number you use here in the -quiport parameter of the idebug command.

If you do not specify class_name when issuing the jdbug command with the ui_daemon_parameters, the debugger will prompt you for the required information in the Load Program dialog of the debugger user interface.

Important: This command applies to version 6 and lower of the debug engine. The version number is displayed when you execute a jdbug or irmtdbgj command. If the debug engine is version 7 or higher, use the irmtdbgj command.

ngrelt.gif (466 bytes)
Starting the debugger for remote debugging
Starting the debugger user interface daemon
Attaching to a running Java Virtual Machine

ngrelr.gif (548 bytes)
idebug command
irmtdbgj command
Supported Java Virtual Machine arguments