Controlling execution with the command-line debugger
When the correlator stops at a breakpoint, you can use the debugger to step over the next line:
engine_debug stepover
However, you most likely want to step over the line, confirm that the correlator stopped, and learn about the current state of the debugger. You can do this by entering multiple commands in one line. For example:
engine_debug stepover wait --timeout 10 status
This is the equivalent of the following three commands:
engine_debug stepover — Causes the debugger to step over one line of EPL.
engine_debug wait --timeout 10 — Causes the debugger to pause until either a breakpoint is hit, or ten seconds pass.
engine_debug status — Displays the debugger's current status.
Following are more examples of entering multiple commands in one line.
engine_debug stepinto wait --timeout 10 status
engine_debug stepout wait --timeout 10 status
To instruct the correlator to continue executing EPL code, run the following command:
engine_debug run
You use the engine_debug run command regardless of how the correlator was stopped — a breakpoint was reached, a step operation, a wait command.
To stop the correlator, enter the following command:
engine_debug stop
Copyright © 2013
Software AG, Darmstadt, Germany and/or Software AG USA Inc., Reston, VA, USA, and/or Terracotta Inc., San Francisco, CA, USA, and/or Software AG (Canada) Inc., Cambridge, Ontario, Canada, and/or, Software AG (UK) Ltd., Derby, United Kingdom, and/or Software A.G. (Israel) Ltd., Or-Yehuda, Israel and/or their licensors.