Выдает следующее (это собственно файл справки):
To launch the emulator, use the following command:
emulator [arguments] [<
APPLICATION>]
The <
APPLICATION> parameter (if present) is the name of the main class, .JAR or .JAD file of the user application. This application starts on the emulator just after the emulator launch. You may use the alternative ways to launch application on the emulator, for example see the -Xjam argument
description below.
The optional parameter "[arguments]" may contain the values from a command line
arguments set. This set includes both arguments from the Sun's "Unified Emulator Interface" and some native arguments. This table contains the Sun's "Unified Emulator Interface" arguments description:
Arguments
Description
-classpath
Set the classpath for the KVM.
-D
<property>=<value>
Set
<property> to
<value>.
-version
Display version information about the emulator.
-help
Display this help.
-Xverbose
This is identical to specifing
-Xverbose:all in the command-line.
-Xverbose:
<type1>[,<type2>[ .. ,<typeN>]]
Write tracing information to the
java.log file for different
<type>s. You can get the tracing information for all types by specifying the
all type.
The <type> may be:
allocation
Trace Java heap allocations and overall heap usage statistics.
gc
Trace Java heap de-allocations .
gcverbose
Detailed garbage collection tracing.
class
Trace class loading, creation and initialization.
classverbose
Detailed tracing of the different class file parts loading into the KVM.
verifier
Trace the KVM internal class verifier.
stackmaps
Trace the behavior of stack maps.
bytecodes
Trace bytecode execution.
methods
Trace entry and exit of every method invoked.
methodsverbose
Detailed method calls tracing.
frames
Trace stack frame pushes and popes.
stackchunks
Trace the allocation of new stack chunks.
exceptions
Trace all thrown exceptions; even if they are caught.
events
Trace the events received by the KVM.
threading
Trace status of all threads in the system.
monitors
Trace program entering of and exiting from a monitor.
networking
Detailed network related methods tracing.
-Xquery
Emulator device information is printed on the standard output; the emulator immediately exits.
WARNING: this command line argument would be correctly processed only if
the emulator is invoked form a DOS box.
-Xdebug
Enable runtime debugging.
-Xrunjdwp must also be specified.
-Xrunjdwp:
<name>=<value>
Starts the JDWP debug session with various sub-options. <name> is one of the sub-option names. Appropriate values for <value> is determined by the sub-option name.
-Xdebug must also be specified.
The <name> may be:
transport
The transport mechanism used to communicate with the debugger. Only the mechanism for
dt_socket value is currently implemented.
address
The transport address for the debugger connection. This can be either
'host:port' or
'port' formats. If the
'port' format used, the host is assumed to be localhost.
server
Start the debug agent as a server. The debugger must connect to the port specified.
suspend
Whether or not the VM should suspend immediately after establishing a connection with the debugger. Values must be either '
y' or '
n'. The default is '
y'.
-Xdevice:
<device_name>
Specify the handset emulator by the <device_name>.
-Xdescriptor:
<jad_file>
Run an application using the specified Java Application Descriptor file.
-Xjam:
<command>=<value>
Run the application manager. The meaning of <value> depends on the command (see below).
The <command> may be:
install
Install the application. The
<value> parameter must be a valid URL of the application descriptor file.
force
The
force command is only valid if invoked in pair with the install command. The
<value> parameter may be either "true" or "false" ("true" if omitted). If its value is "true" and an existing MIDlet has the same storage name as the MIDlet to be installed, the existing MIDlet will be forcefully removed from the device prior to the new MIDlet installation. The "false" value is equivalent to no
force command at all.
The following two commands both enable forceful removal of any existing MIDlet:
-Xjam:install=<application> -Xjam:force=true
-Xjam:install=<application> -Xjam:force
run
Run the previously installed application. The
<value> parameter must be a valid storage name of the MIDlet.
remove
Remove the previously installed application. The
<value> parameter must be a valid storage name of the MIDlet.
transient
Install, run and finally remove an application. The
<value> parameter must be a valid URL of the application descriptor file.
transient is a shortcut for launching the emulator three separate times to install, run and then finally remove the application.
list
List all applications installed on the device. The
<value> parameter must be omitted.
storageNames
List all applications installed on the device in a format easily parsed by another program. The
<value> parameter must be omitted.
This table contains the list of native arguments:
Arguments
Description
/? or /help
Display this help.
/v or /version
Display version information about the emulator.
/sj <file> or /StartJavaApp <file>
Start java application specified by <file>. The <file> parameter may specify a .JAD or .CLASS file.
/dj or /DebugJavaApp
Turn on the emulator's KVM debug mode
/cp <path> or /ClassPath <path>
Change "java class" path registered in a kjava_classpath to <path> (for this session only).
/acp <path> or /APIClassPath <path>
Change "java API class" path registered in kjava_api_classpath to <path> (for this session only).
/l <port> or /DebugProxyPort <port>
Change java debug proxy port number to <port> (for this session only).
/jdk <path> or /JDKHome <path>
Change "JDKHome" path registered in jdk_home to <path>; this path will be used for starting the debug proxy (for this session only).
/tracing
Turn on the tracing mode of the emulator's KVM
/<tracing options>
Set tracing options. See the table of available tracing options hereafter.
The <tracing options> may be:
traceallocation
Trace Java heap allocations and overall heap usage statistics.
tracegc
Trace Java heap de-allocations .
tracegcverbose
Detailed garbage collection tracing.
traceclassloading
Trace class loading, creation and initialization.
traceclassloadingverbose
Detailed tracing of the different class file parts loading into the KVM.
traceverifier
Trace the KVM internal class verifier.
tracestackmaps
Trace the behavior of stack maps.
tracebytecodes
Trace bytecode execution.
tracemethods
Trace entry and exit of every method invoked.
tracemethodsverbose
Detailed method calls tracing.
traceframes
Trace stack frame pushes and popes.
tracestackchunks
Trace the allocation of new stack chunks.
traceexceptions
Trace all thrown exceptions; even if they are caught.
traceevents
Trace the events received by the KVM.
tracethreading
Trace status of all threads in the system.
tracemonitors
Trace program entering of and exiting from a monitor.
tracenetworking
Detailed network related methods tracing.
traceall
Activate all the tracing options above simultaneously
/ShowErrors
Turn on the error report mode.
/ShowInfos
Turn on the information report mode.
!<space><option>.
Turn off the <option> which should be one of the following: /DebugJavaApp, /tracing, /<tracing options>, /ShowErrors and /ShowInfos. E.g.: "! /ShowInfos" (one space after "!" is expected)