What exactly is system debugging?

[Former Member]

Hi SDN,

What exactly is system debugging?

How it is different from normal debugging?

regards,

rahul

[Former Member]

Normal Debugging is Debug your particular program/FM and any other relevant piece of code.

System Debugging is to Monitor the Memory while Debugging.

Hope helps.

Regards

Vinayak

[Former Member]

Hi,

System Debugging

If you set this option, the Debugger is also activated for system programs (programs with status S in their program attributes). When you save breakpoints, the System Debugging setting is also saved.

Normal Debugging

Normal debugging is the one we do it by the normal dynamic break points or by /H or by using stattic break points.

Reward if helpful.

Regards,

Ramya

[Former Member]

hi....

The System Debugging function enables the user to analyze system programs, in addition to application programs, using the Debugger. This function is called or terminated through the menu Settings ® System Debugging On /Off. By selecting the menu Settings ® Save, this predefined setting is stored to the database and thus activated again each time the new Debugger is activated.

The Debugger is a programming tool that you can use to execute ABAP programs, by line or by section. With this tool, you can display data objects and check the flow logic of programs.

At the moment, two types of debugging are possible: Debugging with the classic Debugger for release levels prior to 6.40 or debugging with the new Debugger, which is available for all releases after 6.40. The main differences between the classic and the new ABAP Debuggers are described below:

The new ABAP Debugger is executed in its own external mode (Debugger), while the application to be analyzed (debuggee) uses a second external mode. So far, the application to be analyzed and the debugger itself shared the same roll area of an external mode. For this reason, each action of the Debugger could influence the program flow of the application. Therefore, the classic Debugger cannot use any ABAP statements for designing the user interface. The path for designing modern UI techniques is not available for it.

· With the classic Debugger it is generally not possible to analyze programs in debugging mode that run in an ABAP processor unit and are called recursively from a subordinate unit. For example, a conversion exit cannot be analyzed using the Debugger if it runs within a WRITE statement. However, with the new Debugger this is possible.

The new Debugger provides the user with a flexible interface that can be configured as required and has more than eight desktops. Here it is possible to place and arrange up to four tools - depending on the user's selection. For example, it is possible to display source texts or structures. In this way, the user can design the Debugger interface according to his own individual requirements.

As of Release 6.40, you can select the debugging type as you wish by choosing the classic Debugger or the new Debugger in the ABAP Editor from the path Utilities ® Settings. It is also possible to switch the debugger at any time during a session under the menu option Debugging.

There are plans to make the new Debugger the default option as soon as it contains the following functions, which are currently not available:

Watchpoints

Debugging special types (http, BSP, RFC, update task)

Display of memory consumption

Display of system areas

[Former Member]

Check this SAP help

http://help.sap.com/saphelp_nw04/helpdata/en/ef/5f0640555ae369e10000000a155106/content.htm

[Former Member]

hi Rahul,

The Debugger is a programming tool that you can use to execute ABAP programs, by line or by section. With this tool, you can display data objects and check the flow logic of programs.

The System Debugging function enables the user to analyze system programs, in addition to application programs, using the Debugger. This function is called or terminated through the menu Settings ® System Debugging On /Off. By selecting the menu Settings ® Save, this predefined setting is stored to the database and thus activated again each time the new Debugger is activated.

Update function modules do not run in the same user session as the program that is currently running in the ABAP Debugger. These function modules are therefore not included in debugging. Only if you select the Update Debugging option can you display and debug them after the COMMIT WORK.

Normal debugging is the one we do it by the normal dynamic break points or by /H or by using stattic break points.

You can switch to diffferent debugging modes while processing.

Reward if useful.

Thankyou,

Regards.