JSwat supports tracing methods. A trace is a breakpoint that is hit every time any method is entered or exited. As you might imagine, this generates a lot of events. Thus, it is vitally important that the trace has a class and/or thread filter. See the breakpoints help for the section on setting up filters.
By default, the trace breakpoint does not suspend the debuggee VM. It would be rather useless to do so, but the option is available via the breakpoint properties dialog box.
The trace
command can be used to create a trace.
There is also a dialog box available from the "Trace
Methods" menu item in the "Breakpoints" menu. You
are required to specify the name of a class to act as the class
filter. You could specify 'all
' but I do not
recommend it.
Although trace breakpoints are like any other breakpoint and support conditions and monitors, it has not been tested. At the very least, the suspend policy has to be changed from "none" to either "thread" or "all".