Introduction to the ABAP Debugger

The debugger is used to execute ABAPProgramProgramming tools, can be executed by line or by node. This tool can be used to display data objects and check the logic flow of programs.

Now, you can use two types of debuggers: Traditional debuggers that are compatible with versions earlier than 6.40, and new debuggers that are later than 6.40. The following are the main differences between the two debuggers.

• The new version of the ABAP debugger runs in its own extension mode (debugger), while the analyzed application (debugging object) uses another extension mode. So far, the debugged application and the debugger share the same region of the same extension mode. Therefore, each action of the debugger may affect the application stream. In this way, the traditional debugger cannot use any ABAP statements designed for user interfaces. The path for designing modern user interface technology cannot be used.
• Using a traditional debugger, it is generally impossible to analyze programs that run on the ABAP processor unit and are recursively called from a lower-level unit in the debugging mode. For example, if a conversion exit is run in a Write statement, it cannot be analyzed. However, this can be done with the new debugger.
• The new debugger provides users with more flexible interfaces, which can be configured as needed and have more than 8 desktops. You can select four tools for placement and arrangement. For example, you can displaySource codeOr structure. In this way, you can design the debugger interface based on your own independent needs.

In version 6.40, you can select "utility-> Settings" in the ABAP editor to select which debugger to use. You can also use the "debug" menu to switch between debuggers during the debugging process.

Note:
The new debugger has the following functions, but the current version does not.

1. Observation Point
2. Debugging special types (HTTP, BSP, RFC, and update tasks)
3. Display memory consumption
4. Show System regions