IBM User Guide for Java V7 on Windows > Troubleshooting and support > Using diagnostic tools > Tracing Java applications and the JVM > Controlling the trace > Detailed descriptions of trace options > Options that control tracepoint activation

Tracepoint specification

You enable tracepoints by specifying component and tracepoint.

If no qualifier parameters are entered, all tracepoints are enabled, except for exception.output trace, where the default is all {exception}.

The <tracepoint_specification> is as follows:

[!]<component>[{<type>}] or [!]<tracepoint_id>[,<tracepoint_id>]

where:

!

is a logical not. That is, the tracepoints that are in a specification starting with ! are turned off.

<component>

is a Javaâ„¢ subcomponent, as detailed in Table 1. To include all Java subcomponents, specify all.

Table 1. Java subcomponents

Subcomponent name	Description
avl	VM AVL tree support
j9bcu	VM byte code utilities
j9bcverify	VM byte code verification
j9codertvm	VM byte code run time
j9dmp	VM dump
j9jcl	VM class libraries
j9jit	VM JIT interface
j9jvmti	VM JVMTI support
j9mm	VM memory management
j9prt	VM port library
j9scar	VM class library interface
j9shr	VM shared classes
j9trc	VM trace
j9util	VM utilities
j9vm	VM general
j9vmutil	VM utilities
j9vrb	VM verbose stack walker
map	VM mapped memory support
mt	Java methods (see note)
pool	VM storage pool support
rpc	VM RPC support
simplepool	VM storage pool support
sunvmi	VM class library interface

Note: When specifying the mt subcomponent you must also specify the methods option.

<type>

is the tracepoint type or group. The following types are supported:

• Entry
• Exit
• Event
• Exception
• Mem
• A group of tracepoints that have been specified by use of a group name. For example, nativeMethods select the group of tracepoints in MT (Method Trace) that relate to native methods. The following groups are supported:
  • compiledMethods
  • nativeMethods
  • staticMethods

<tracepoint_id>

is the tracepoint identifier. The tracepoint identifier constitutes the component name of the tracepoint, followed by its integer number inside that component. For example, j9mm.49, j9shr.20-29, j9vm.15, To understand these numbers, see Determining the tracepoint ID of a tracepoint.

Some tracepoints can be both an exit and an exception; that is, the function ended with an error. If you specify either exit or exception, these tracepoints are included.

The following tracepoint specification used in Java 5.0 and earlier IBM SDKs is still supported:

[!]tpnid{<tracepoint_id>[,...]}

Examples

• All tracepoints:

  -Xtrace:maximal=all

• All tracepoints except j9vrb and j9trc:

  -Xtrace:minimal={all},minimal={!j9vrb,j9trc}

• All entry and exit tracepoints in j9bcu:

  -Xtrace:maximal={j9bcu{entry},j9bcu{exit}}

• All tracepoints in j9mm except tracepoints 20-30:

  -Xtrace:maximal=j9mm,maximal=!j9mm.20-30

• Tracepoints j9prt.5 through j9prt.15:

  -Xtrace:print=j9prt.5-15

• All j9trc tracepoints:

  -Xtrace:count=j9trc 

• All entry and exit tracepoints:

  -Xtrace:external={all{entry},all{exit}}

Parent: Options that control tracepoint activation

Error 404 - Not Found

The document you are looking for may have been removed or re-named. Please contact the web site owner for further assistance.