Once the debugger is activated and attached to a session, a break event must occur to cause the debug trace and associated data display to begin. Break events include (but are not limited to) the following:
- An error occurs that would cause object execution to be terminated
- A previously set breakpoint is reached during processing
- The record is read when the Break on Record Write break rule is active
- The Pause icon is clicked in the popup of the debugger page
Of the preceding events, the two most common methods of starting up a debug trace are the first two, an error, or reaching a previously set breakpoint. If, for example, an error condition is discovered in an operating object, the debugging process can be initiated by doing the following:
- Activating the debugger
- Running the process where the error occurs
When the error occurs, the page parts (Variables, Watches, and Call Stack) in the debug window will be populated, and we can proceed to investigate variable...