The Debug view allows you to manage the debugging of a rule project or any Java program in the workbench. It displays the stack frame for the suspended threads for each target you are debugging. Each thread appears as a node in the tree.

The Debug view does not provide a history of all the events occurring in the rule engine. However, a stack trace is a useful debugging tool, particularly when an exception has been thrown in the code, or when you have a method that is called from a variety of places within your code and you want to learn where it is being called from when a particular problem occurs.

You can get stack trace information of the execution history, that is, the names of the classes and methods within those classes that had been called at the point when the exception occurred through programmatic access. For example, you can use the StackTraceElement class, and the getStackTrace method of the Throwable class.

You can also generate a partial Java stack trace by using the static Thread.dumpStack method, or the printStackTrace method of the Throwable class.

If the JVM experienced an internal error it will call its own signal handler to print out the threads and monitors information.

Related Concepts

Related Tasks

Related Samples and Tutorials