Script Debugger status

The Script Debugger status determines what debugging actions are available and what information it can display.

The Script Debugger displays its status at the bottom left of the user interface.

Figure 1. Sample Script Debugger status
The Script Debugger Status field showing the sample status EXECUTION_PAUSED
Table 1. Possible Script Debugger status values
Status Occurs when Description Actions available
WAITING_FOR_FIRST_BREAKPOINT
  • The user opens a Script Debugger window or tab.
The Script Debugger is ready to pause script and display debugging information.
  • Pause script at the first breakpoint in the call stack.
EXECUTION_PAUSED
  • The Script Debugger pauses on a breakpoint.
  • The user steps over, steps into, or steps out to the next line of evaluated code.
The Script Debugger has paused on a line of code, and the user can debug the script.
  • Resume processing until the Script Debugger reaches the next breakpoint.
  • Step through a script.
  • Display the call stack.
  • Display transaction information.
  • Display variable values.
WAITING_FOR_BREAKPOINT
  • The user resumes processing until the Script Debugger reaches the next breakpoint.
  • The user steps through a script until the Script Debugger reaches the next line of code to evaluate or the transaction completes.
The Script Debugger is searching for the next line of code at which to pause. Users will typically never see this status because the Script Debugger changes status after it locates the next breakpoint or script line to evaluate.
  • Pause script at the next breakpoint.
  • Pause script at the next script line requiring evaluation.
OFF
  • The user pauses the Script Debugger.
  • The user closes the Script Debugger window or tab.
  • The user session ends for any reason.
  • The administrator resets all Script Debugger instances by navigating to the debugger_reset.do page.
The Script Debugger is inactive and does not pause scripts or display debugging information.
  • Start the Script Debugger.
  • Open a Script Debugger window or tab.

Log entries

Every time a debug transaction finishes executing, the system creates a log entry for it with a DEBUGGED prefix. For example:

2016-08-15 15:57:32 (197) Default-thread-3 900F510167112200C4098C7942415A75 *** End
#39, path: /my-app.do, user: admin, DEBUGGED total transaction time: 0:00:11.010,
transaction processing time: 0:00:11.010, network: 0:00:00.000, chars: 6,058, uncompressed
chars: 20,731, SQL time: 50 (count: 34), business rule: 0 (count: 0), phase 1 
form length 56,464, largest chunk written: 10,428, request parms size: 40, largest input read: 0