Debugger (Magic xpa 3.x)

« Go Back


Created ByKnowledge Migration User
Approval Process StatusPublished

Debugger (Magic xpa 3.x)

This feature can help you pinpoint problems that you are having in an application.

When you are in Debug mode (you selected Debug Mode from the Debug menu), you can run a program in Runtime mode and the Debugger will park on the Studio read-only screen at the exact location of where you are in the program (when a breakpoint is reached).

In the Debugger you can:

  • View breakpoints and variable values within the task flow view. Breakpoints enable you to halt execution of the program at a specific location in the Studio screen.

  • View the Magic xpa flow within the Studio using the Activity Monitor.

  • Set conditions for the breakpoints.

  • Create a Watch list that includes selected variables to be watched during runtime.

  • Update variable values during deployment. When you update a value in the Debugger, you are prompted to confirm recomputation.

  • View the flow from within the Studio.

  • View the call stack.

  • Switch between different contexts for debugging.

  • Dynamically handle logs using the Logging function.

  • Execute the Debugger remotely.

For a more detailed description of the options provided by the Debugger, please see the Debugging Options topic.

How the Debugger Saves

The Debugger saves the following between sessions: Breakpoints, Breakpoint sort order, Watched variables, and Call stacks.

These items will be saved in a local file that will be saved next to the project file. This file will have the following name:

<project file name>.opt

This file will not be saved in the project's source safe.

Rich Client Tasks

For Rich Client tasks, the Debugger supports server-side debugging (Since version: 1.9).

A breakpoint on a server-side action (or a neutral-side action that is performed on the server side) will cause the engine to halt and wait for the developer. A breakpoint on a client-side action (or a neutral-side action that is performed on the client side) will be ignored. Break Now will break during the next server access.

When performing Step to a Client operation, the Debugger will halt again after going back to the server, so if there are several client actions, they will be performed without interference from the Debugger.

Related Topics