Using the Debug view

With the Debug view, you can manage the debugging of a program in the workbench. It displays the stack frame for the suspended thread for each target you are debugging. If the thread is suspended, its stack frames are shown as child elements.

If the resource containing a selected thread is not open and/or active, the file opens in the editor and becomes active, focusing on the source with which the thread is associated.

In the Debug view, you can perform various start, step, and terminate debug actions. For more information about these actions, see the related topics.

To suspend a thread in the stack frame that is currently running, click the Debug view Suspend button (Suspend button) or choose Run > Suspend from the workbench menu bar.

An XSL transformation actually runs in a JVM. Because of this, and because you can use the XSLT debugger to debug Java™ extensions called from your XSL transformation, the Debug view displays JVM threads as if you were debugging a Java application. The XSL transformation will run on the main thread in the JVM. When the transformation suspends on a breakpoint or at the end of a step request, the main thread will suspend and show the stack frames for the XSL transformation. For information about debugging Java extensions and XSL transformations called from Java, see the related topic. In this and other help topics, thread will refer to the Java thread that is executing the XSL transformation.

Related tasks
Stepping through a program
Debugging Java extensions called from XSL transformations
Terminating a debug session
Running XSL transformations during a debug session

Feedback