Working with breakpoints using the command-line debugger
You can use the command-line debugger to add, list and remove breakpoints.
Adding breakpoints
There are two ways to add a breakpoint. If you know the EPL file name and the line number, you can enter something like the following:
engine_debug breakpoint add --file filename.mon --line 27
When you specify a file name, you must specify the exact path you specified when you injected the monitor. For example, suppose you ran the following:
engine_inject foo.mon
You can then specify foo.mon for the file name. Now suppose you ran this:
engine_inject c:\foo\bar\baz.mon
You must then specify c:\foo\bar\baz.mon for the file name.
If you prefer to use the monitor and action name, along with the line number, enter something like this:
engine_debug breakpoint add --monitor package.monitor --action actionName
--line 27
The debugger output indicates the line number where it added the breakpoint. In some cases, the debugger does not set the breakpoint on the line you specified, for example, when a statement runs over multiple lines.
Listing breakpoints
To obtain a list of the breakpoints currently set in the correlator, enter the following:
engine_debug breakpoint list
Removing breakpoints
To remove a breakpoint by specifying the file name and the line number, enter something like the following:
engine_debug breakpoint delete --file filename.mon --line 27
To use the monitor name to remove a breakpoint, enter something like this:
engine_debug breakpoint delete --monitor package.monitor --action actionName
--line 27
To delete a breakpoint by using the breakpoint ID that appears in the breakpoint list returned by the debugger, enter something like this:
engine_debug breakpoint delete --breakpoint 1
Contact Support
|
Community
|
Feedback