The idebug command
starts both the Distributed Debugger interface and the debug engine when debugging a
program locally. When debugging remotely, it is used to connect to a debug engine daemon
on a remote system or to start the debugger user interface as a daemon on your local
system.
The idebug command has the following syntax for AIX or Windows:
idebug [idebug_options] [local_debug_parameters | remote_debug_parameters | ui_daemon_parameters] [--] [program_name [program_parameters]]
The idebug_options are zero or more of the following:
Option | Purpose |
---|---|
-a process_id | Attach to the already running process process_id.
|
![]() |
Start debugging the specified child process of the program being debugged. This option only applies to the program you are debugging on OS/2, and is ignored on other platforms. |
-h or -? | Display help for the idebug command. |
-i | Start the debugger in the system initialization code that
precedes the call to the main entry point for the program.
|
-p+ | Use program profile information. The debugger will restore
window sizes, positions, fonts, and breakpoints for your program from the last time you
debugged the program. If you are debugging the program for the first time, the debugger
windows start up with their default appearance, and no breakpoints are set. Any changes you make to the windows and breakpoints are saved. Note: If you add or delete lines in your source file, recompile it, and then debug the program again with a saved program profile, line breakpoints may no longer match the code they were initially set for because line breakpoint information is saved by line number, not by the content of the line. If the debugger has saved a profile containing information on window, breakpoint, and monitor settings from a previous debug session for this program, the profile is used to restore those settings. This is the default setting for the debugger. |
-p- | Do not use program profile information. The debugger ignores
any program profile information, and the debugger windows start up with their default
appearance, and no breakpoints are initially set.
|
-qquiet | Suppresses the splash screen when the debugger starts. |
-s | Prevents the debugger from stopping in the first debuggable
statement in the program. Program execution only stops when the first set breakpoint is
encountered. This option requires that the program you want to debug has program profile information available. If no program profile information is available, or you specify the -p- option, the program will run to completion. |
Use the local_debug_parameters when you want to start debugging a program on your local system. If a parameter is not specified in the command, the default is assumed.
The local_debug_parameters are:
Parameter | Description | ||||||||
---|---|---|---|---|---|---|---|---|---|
![]() |
This parameter can only be used when debugging interpreted Java programs. Specifies a temporary classpath for the debugger to use to find the Java classes you are debugging. If this is not specified, the debugger uses your present CLASSPATH environment variable setting to find the Java classes you are debugging. |
||||||||
![]() <jvm_arguments> |
This parameter can only used when debugging interpreted Java programs. Specifies the arguments passed to the JVM that will run the program you want to debug. If you specify more than one option, enclose the list of options in quotation marks. For a list of supported JVM arguments, see the related topic below. |
||||||||
![]() ![]() <dominant_language> |
Specifies the dominant language to use for debugging. Valid values for <dominant_language> are:
|
Use the remote_debug_parameters when you want to connect to a debug engine daemon on a remote system. If a parameter is not specified in the command, the default is assumed.
The remote_debug_parameters are:
Parameter | Description | ||||||||
---|---|---|---|---|---|---|---|---|---|
![]() |
This parameter can only be used when debugging interpreted Java programs. Specifies a temporary classpath for the debugger to use to find the Java classes you are debugging. If this is not specified, the debugger uses your present CLASSPATH environment variable setting to find the Java classes you are debugging. |
||||||||
![]() ![]() |
Specifies the TCP/IP name or address of the machine where the debug engine
is running. This parameter is required when debugging remotely. |
||||||||
![]() <jvm_arguments> |
This parameter can only used when debugging interpreted Java programs. Specifies the arguments passed to the JVM that will run the program you want to debug. If you specify more than one option, enclose the list of options in quotation marks. For a list of supported JVM arguments, see the related topic below. |
||||||||
![]() ![]() <dominant_language> |
Specifies the dominant language to use for debugging. These are the valid values for <dominant_language>:
|
||||||||
![]() ![]() |
Specifies the port number on the machine where the debug engine is
running. The default port is 8000. This port number must match the port number used in the -qport parameter of the irmtdbgc command.
|
The ui_daemon_parameters are used when starting the Distributed Debugger user interface as a daemon. When running as a daemon, the Distributed Debugger user interface listens on a specific port number for a debug engine. Once a connection is made, the Distributed Debugger user interface appears and you can begin debugging your program. The ui_daemon_parameters are:
Parameter | Description | ||||||||
---|---|---|---|---|---|---|---|---|---|
-qdaemon | Tells the Distributed Debugger user interface to run as a daemon. You must
use the -quiport option when specifying -qdaemon.
|
||||||||
-qlang= <dominant_language> |
Specifies the dominant language to use for debugging.
These are the valid values for <dominant_language>:
|
||||||||
-quiport=<port> | Specifies the port numbers where the Distributed Debugger user interface
daemon should listen for a debug engine. You can specify a single port or multiple ports.
When specifying multiple ports, <port> must be a comma-delimited list
of port numbers. This option is required when using the -qdaemon option. There is no default port number.
|
||||||||
-qterminate | Closes any running Debugger user interface daemons before starting a new user interface daemon. |
Use the "--"
parameter to separate debugger options and parameters from the program name and
parameters. Use this option if your program name or parameters include forward slashes
("/") or dashes ("-"). If you do not use this option, anything
preceded by a slash or a dash will be interpreted as a debugger option.
If you do not specify program_name when issuing the idebug command, the debugger will prompt you for the required information in the Load Program dialog.
Starting the debugger for
local debugging
Starting the debugger for
remote debugging
Attaching to a running Java Virtual Machine
Starting the debugger on Solaris
irmtdbgc command
irmtdbgj
command
Supported
Java Virtual Machine arguments
jdbug
command