IBM User Guide for Java V7 on Windows > Troubleshooting and support > Using diagnostic tools > Tracing Java applications and the JVM

Using method trace

Method trace is a powerful tool for tracing methods in any Java™ code.

Method trace provides a comprehensive and detailed diagnosis of code paths inside your application, and also inside the system classes. You do not have to add any hooks or calls to existing code. You can focus on interesting code by using wild cards and filtering to control method trace.

Method trace can trace:

• Method entry
• Method exit

Use method trace to debug and trace application code and the system classes provided with the JVM.

While method trace is powerful, it also has a cost. Application throughput is affected by method trace. Additionally, trace output is reasonably large and might require a large amount of drive space. For instance, a full method trace of a "Hello World" application is over 10 MB.

• Running with method trace
  Control method trace by using the command-line option -Xtrace:<option>.
• Untraceable methods
  Internal Native Library (INL) native methods inside the JVM cannot be traced because they are not implemented using JNI. The list of methods that are not traceable is subject to change without notice between releases.
• Examples of use
  Here are some examples of method trace commands and their results.
• Example of method trace output
  An example of method trace output.

Parent: Tracing Java applications and the JVM

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.