Run Dialog
The Run Dialog is displayed from the Target menu
in the Menu Bar.
The Run Dialog allows the User to debug a given Java program
in a target JVM. The resulting standard input/output/error streams from
the target JVM are displayed in the Input/Output Panel.
The Target Info Dialog displays information about the target JVM
once the debugger is connected.
fields
- Class containing main() - the class name (including package names) of the class containing
the main() method in which to start executing the Java program to be
debugged in the target JVM.
The ... button displays a dialog
containing a history list of previous entries to select from.
- main() Arguments [optional] - the command line arguments to pass to the
main() method.
The ... button displays a dialog
containing a history list of previous entries to select from.
- CLASSPATH - the classpath for the target JVM to use.
If not specified, the CLASSPATH environment variable (or equivalent for your Java platform)
will be used.
The ... button displays the CLASSPATH Dialog.
If the entered classpath contains a space (for example in c:\Program Files)
and the Quote character field (see below) is blank, and there is no double quote character
in the classpath already, then the entire classpath will be
surrounded by double quotes (behind the scenes) in order to correctly handle the space(s).
- Additional JVM arguments [optional] - any additional target JVM arguments.
The ... button displays a dialog
containing a history list of previous entries to select from.
- Quote character [optional] -
the character used to combine space-delimited text on the command line.
Defaults to the double quote character ".
For example for the main() Arguments, "test arg" (surrounded by the
explicit double quotes) would be passed to main()
as one argument (with the double quotes stripped off), not two arguments.
Or as another example for the CLASSPATH, "c:\Program Files\example1.jar;c:\Program
Files\example2.jar" (surrounded by the explicit double quotes) would handle
the space correctly between Program Files in this CLASSPATH example.
check boxes
- Breakpoint at main() - if checked, set a breakpoint at the beginning of the main()
method.
- Classic JVM (no Hot Spot) - if checked, use the Classic JVM as the target JVM
instead of the Hot Spot JVM.
The Classic JVM exists only prior to J2SDK 1.4.
The Classic JVM has faster and more reliable debugging performance
prior to J2SDK 1.4. Check only if your target JVM supports the -classic flag.
buttons
- OK - runs the specified Java program
in a target JVM. If there is an error, an error message dialog will be displayed, outlining
possible Run Errors.
- Cancel - closes the dialog without
running a Java program in a target JVM.
- Help - displays this Help.
©2001-2010. debugtools.com LLC. All rights reserved