topic Re: debugging in Application Development and Automation Discussions

debugging

Former Member — Thu, 11 Jan 2007 08:39:01 GMT

what is debugging?types of debugging?watchpoint ?breakpoint?

Re: debugging

Former Member — Thu, 11 Jan 2007 08:41:45 GMT

3 types update,normal and system debugging

check this for update debugging

If you set "Update Debbugging" you can debug the codes which works in update tusk.

SAP std often runs the routine (function or form) to update the database in update tusk mode, these routine start as soon as a commit work is done.

The commit is called at the end of the program, so you can't debug them by "normal debbugging" because it ends as soon as the program ends

or----

All the database updates are performed by the update work processes by calling the functions/subroutines in update tasks.

These tasks are executed after a commit work is reached in the application. By default you cannot debug these functions.

TO debug these u need to explicitly activate update debugging.

for system debugging check the below link

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

http://help.sap.com/saphelp_47x200/helpdata/en/c6/617ca9e68c11d2b2ab080009b43351/frameset.htm

For debugging tutorial:

http://help.sap.com/saphelp_erp2005vp/helpdata/en/5a/4ed93f130f9215e10000000a155106/frameset.htm

http://www.sapdevelopment.co.uk/tips/debug/debughome.htm

http://www.sap-basis-abap.com/sapab002.htm

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.

Update Debugging

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

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 debuggin modes while processing.

<b>BREAKPOINT</b>

In the source code we set the Break-point there by clicking the stop button, the system will stop there when you execute the program.

<b>Watchpoint</b>

For watchpoints, we need to give some condition and when this condition is satisfied, program will stop

example : if you want to debug only

for matnr value 100 than set watch point

matnr = 100. when value reaches 100 than

program stops at that point.

more at

http://help.sap.com/saphelp_nw04/helpdata/en/c6/617cdce68c11d2b2ab080009b43351/content.htm

Re: debugging

Former Member — Thu, 11 Jan 2007 08:42:25 GMT

Please read SAP help . Otherwise ref some sap siites.

regards,anjireddi

Re: debugging

Former Member — Thu, 11 Jan 2007 08:45:01 GMT

Hi sunil,

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.

Two types of debugging are currently possible:

Debugging with the classic Debugger for release levels up to and including 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 Classic ABAP Debugger
runs in the same roll area as the application to be analyzed (debuggee). It is therefore displayed in the same window as the application. However, this technology also has some restrictions. For example, some ABAP programs (such as conversion exist) cannot be analyzed in debug mode for technical reasons. However, the most significant restriction is that no ABAP technology can be used for designing the Debugger interface and it is therefore not possible to create a modern user interface.

* The New ABAP Debugger,
on the other hand, is executed in a separate external session (Debugger), while the application to be analyzed (debuggee) uses a second external session. With this technology, the user interface of the Debugger can be designed freely by ABAP means.
Breakpoints Locate the document in its SAP Library structure

Apart from being able to execute an ABAP program in the Debugger, you can also start the Debugger call by the choosing a breakpoint.
This is achieved by setting one or more of these breakpoints in the program. A breakpoint is a signal at a particular point in the program that tells the ABAP runtime processor to interrupt processing and start the Debugger. The Debugger is activated when the program reaches this point.

Like a breakpoint, a watchpoint is an indicator in a program that tells the ABAP runtime processor to interrupt the program at a particular point. Unlike breakpoints, however, watchpoints
are not activated until the contents of a specified field change. Watchpoints, like dynamic breakpoints, are user-specific, and so do not affect other users running the same program. You can only define watchpoints in the Debugger.

http://help.sap.com/saphelp_nw2004s/helpdata/en/c6/617ca9e68c11d2b2ab080009b43351/frameset.htm

Re: debugging

Former Member — Thu, 11 Jan 2007 08:49:38 GMT

Have a look at below link.

https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/9cbb7716-0a01-0010-58b1-a2ddd8361ac0

I hope it helps.

Best Regards,

Vibha

*Please mark all the helpful answers

Re: debugging

Former Member — Thu, 11 Jan 2007 09:24:34 GMT

hi Sunil,

You haven't marked any points to me on to your previous question . Please mark the helpful answers and close the thread if answered ..

Regards,

Santosh

Re: debugging

Former Member — Tue, 05 Aug 2014 06:13:51 GMT

Hi,

Debugging is an integrated test tool that allows you to check the program logic and to find errors in the source code of an ABAP program. The running program is interrupted after each step, allowing you to check its processing logic and the results of individual statements.

Types of Debugging:

1] Classic Debugger

2] New Debugger

1] Classic Debugger: The Classic Debugger runs in the same internal session of the same external session as the application you are analyzing i.e Debugger and Debugee runs in the same (internal) session.

2] New Debugger: New ABAP Debugger uses uses two separate sessions for the debugger and the application. It is the more robust Debugger architecture with less risks involved and is faster than classic debugger.

Breakpoint: A breakpoint is a signal in a line of code that tells the ABAP runtime processor to interrupt the program at that line and start the ABAP Debugger.

Static Breakpoint: Static breakpoints are not normally user-specific. Once a user has inserted a BREAK-POINT statement in an ABAP program, the system always interrupts the program at that point. You should only use static breakpoints during the development phase of an application.

Dynamic Breakpoint: Dynamic breakpoints are user-specific. You should, therefore, use them when you only want the program to be interrupted when you run it yourself. All dynamic breakpoints are deleted when you log off from the R/3 System.

Watchpoint: Like a breakpoint, a watchpoint is an indicator in a program that tells the ABAP runtime processor to interrupt the program at a particular point. Unlike breakpoints, however, watchpoints are not activated until the contents of a specified field change.

You set watchpoints in the Debugger to monitor the contents of specific fields. They inform you when the value of a field changes. When the value changes, the Debugger interrupts the program.