Settings  

Use

You use the settings to set the debugging mode of a program.

To open the Debugger Settings dialog box, choose Settings → Display/Change Debugger Settings.

Features

Debug Modes

●      System Debugging

System Debuggingenables you to debug system programs.

When you save breakpoints, the System Debugging setting is stored in the database and activated again each time you start the Debugger.

●      Update Debugging

Update function modules are not included in debugging and do not run in the same user session as the program that is currently running in the Debugger. If you select Update Debugging, you can display and debug update function modules after you execute a COMMIT WORK.

●      TRFC (In Background Task): Block Sending

When you debug a program that calls function modules using the IN BACKGROUND TASK addition, they are processed in a background work process (additional internal session).

If you select the setting, the system collects the function calls but does not start the background work process. The Debugger assigns a transaction ID that identifies the background work process uniquely. Afterwards, you can start the background work process using transaction SM58.

●      ESI Debugging

You select this checkbox if you want to debug a service triggered by ESI.

●      Shared Objects: Debug Automating Area Structuring

You select this checkbox if you want the Debugger to start automatically for the process that is creating the shared object area.

Specific Settings

●      Close the Debugger after ‘Continue’(F8) and Roll Area End.

●      Automatically Copy Session BPs.

●      Always Create Exception Obj..

This setting creates exception objects for class-based exceptions.

If the INTO ref addition is missing in the CATCH statement, you can create an exception object in the Debugger.

When an exception occurs, a message appears in the status bar and two additional icons appear in the display with the quick info texts Display Exception Object and Statement that Caused the Exception.

○       If you choose Display Exception Object, the system displays the attributes and interfaces of the exception class together with their contents. The text description key that is assigned to the exception is displayed in a quick info text with the name of the constant that was generated for this key.

○       For example, depending on whether the exception occurred when reading or writing, the system displays READ_ERROR or WRITE_ERROR in a quick info text for the attribute TEXTID with exception of type CX_SY_FILE_IO.

○       If you choose Statement that Caused the Exception, the system displays the line of the source code containing the statement that caused the exception. The statement is marked in the source code.

●      Cross-Roll-Area Stack Active

If you select this setting, the system starts to record the call stack when the internal session changes. If you do not select it, the call stack displays only the stack of the current internal session.

●      Check Sorting Before READ BINARY SEARCH

If you select this setting, the system checks whether the internal table is sorted before every execution of the statement. If the table is not sorted, a runtime error occurs. You should activate this setting only shortly before reaching the point in the source code, because there can be a significant loss in performance depending on the table size.

Validity of Settings

The settings in the Debugger have the following validity:

●      System and Update Debugging and Always Create Exception Object are valid in external sessions.

System Debugging and Always Create Exception Object are saved when breakpoints are saved and are valid in the current user session.

These settings are also copied to HTTP and Update sessions.

●      TRFC (In Background Task): Block Sending is valid in internalsessions only.