NonStop Server for Java Tools Reference (NSJ 4.2+)

stop in java.lang.String.length (sets a breakpoint at the
beginning of the method java.lang.String.length)
●
stop in MyClass.init (init identifies the MyClass constructor)●
stop in MyClass.clinit (clinit identifies the static initialization
code for MyClass)
●
If a method is overloaded, you must also specify its argument types so that the
proper method can be selected for a breakpoint. For example,
MyClass.myMethod(int,java.lang.String), or
MyClass.myMethod().
The clear command removes breakpoints by using a syntax as in clear
MyClass:45. Using the clear command with no argument displays a list of all
breakpoints currently set. The cont command continues execution.
Stepping
The step command advances execution to the next line whether it is in the
current stack frame or a called method. The next command advances execution to
the next line in the current stack frame.
Exceptions
When an exception occurs for which there is not a catch statement anywhere in
the throwing thread's call stack, the Java VM normally prints an exception trace
and exits. When running under jdb, however, control returns to jdb at the
offending throw. You can then use jdb to diagnose the cause of the exception.
Use the catch command to cause the debugged application to stop at other
thrown exceptions, for example: catch
java.io.FileNotFoundException or catch
mypackage.BigTroubleException. Any exception that is an instance of
the specified class (or of a subclass) stops the application at the point where it is
thrown.
The ignore command negates the effect of a previous catch command.
Note: The ignore does not cause the debugged VM to ignore
specific exceptions, only the debugger.