wt is watchPoints....?

former_member198441 · ‎11-01-2007

Wt is a watchPoint ..?

Compare WatchPoint and a BreakPoint...?

need fulll info reagrding the <b>ABAP Debugger</b>

regards,

Prashanth

Former Member · ‎11-01-2007

Hi,

Check the standard sap help

http://help.sap.com/saphelp_nw2004s/helpdata/en/f1/792442db42e22ce10000000a1550b0/content.htm

Thanks

Naren

kiran_k8 · ‎11-01-2007

Prashanth,

No need to give points,got it from SDN itself.

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.

Use

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.

Features

· You can set up to five watchpoints in a program.

See also Specifying Logical Links.

· You can define watchpoints as either local or global. If you define a global watchpoint, it is active in all called programs. Local watchpoints are only active in

the specified program.

· You can change and delete watchpoints.

See Changing Watchpoints

· You can use watchpoints to display changes to the references of strings, data and object references, and internal tables.

See Memory Monitoring with Watchpoints

Breakpoints

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.

There is also a special kind of breakpoint called a watchpoint. When you use watchpoints, the Debugger is not activated until the contents of a particular field change. For more information, refer to the chapter Watchpoints.

Breakpoint Variants

The Debugger contains different breakpoint variants:

Static

A user-specific breakpoint is inserted in the source code as an ABAP statement using the keyword BREAK-POINT. A non user-specific breakpoint is set in the ABAP Editor using the BREAK user name statement.

Directly set

dynamic breakpoints

Can be set in the ABAP Editor or the Debugger by double-clicking a line, for example. Dynamic breakpoints are always user-specific, and are deleted when you log off from the R/3 System.

Breakpoints

at statements

The Debugger stops the program immediately before the specified statement is executed.

Breakpoints

at subroutines

The Debugger stops the program immediately before the specified subroutine is called.

Breakpoints at function modules

The Debugger stops the program immediately before the specified function module is called.

Breakpoints at methods

The Debugger stops the program immediately before the specified method is called.

Breakpoints at exceptions and system exceptions

The Debugger stops the program immediately after a system exception, that is, after a runtime error has been intercepted.

Static Breakpoints

Static breakpoints are always user-independent if there is no specification of a user name. Once a user has inserted the statement BREAK-POINT or BREAK name in an ABAP program, the system always interrupts the program at that point for that user or only for the user name. This procedure is only useful in the development phase of an application when program execution is always to be interrupted at the same place. For more information, refer to the chapter Static Breakpoints.

In HTTP sessions, a static breakpoint is skipped if you did not set additional dynamic HTTP breakpoints in the editor of a BSP page. Instead, a corresponding system log entry is written, which can be checked using transaction SM21.

Dynamic Breakpoints

Dynamic breakpoints are user-specific. Therefore, you should use them if you only want the program to be interrupted when you run it yourself, not when it is being executed by other users. All dynamic breakpoints are deleted when you log off from the R/3 System.

Dynamic breakpoints are more flexible than static breakpoints because you can deactivate or delete them at runtime. They have the following advantages:

· You do not have to change the program code.

· You can set them even when the program is locked by another programmer.

· You can define a counter that only activates the breakpoint after it has been reached.

Special dynamic breakpoints are useful when you want to interrupt a program directly before a particular ABAP statement, a subroutine, or an event, but do not know exactly where to find it in the source code. Event here is used to refer to the occurrence of a particular statement, for example, or calling up a method. Special dynamic breakpoints are user-specific. You can only set them in the Debugger. For more information, refer to the chapter Dynamic Breakpoints.

In HTTP sessions, the system stops both at static and dynamic breakpoints if a dynamic breakpoint was set in the editor of a BSP page before program execution.

Lifetime and Transfer of Breakpoints

A static breakpoint remains intact as long as the BREAK-POINT or BREAK-POINT name statement is not removed from the source code. Without saving, dynamic breakpoints only remain intact in the relevant internal session. However, they remain in effect during the entire user session if they are saved by choosing the menu path Breakpoints ® Save in the ABAP Debugger. For more details on the subject of user sessions and modes, refer to Modularization Techniques in the ABAP keyword documentation.

If you call an HTTP session during a user session, only the HTTP breakpoints are loaded when the HTTP session is started. You activate HTTP debugging in the ABAP Editor by choosing Utilities ® Settings ® HTTP Debugging. Depending on the setting, the system then displays either the HTTP or standard breakpoints in the Editor.

If you call an update session during a user session, breakpoints that were defined beforehand in the calling processing unit are copied to the new update session, where they can be displayed under Breakpoints. If, in the ABAP Debugger, you check Update Debugging under Settings and then, for example, call the update module func using CALL FUNCTION func IN UPDATE TASK, a new window is opened in which you can debug this function module in the update session. All the breakpoints that were set in the calling processing unit can also be processed here.

we can keep them at :

Statements

Subroutines

Function Module Calls

at Methods

System Exceptions

break point :

we can start debugging from that point or if we keep break point at some place we can directly got ot htat point using f6.

watch point: for example if we have to check the output for 4000 records based on a field value i.e.for vendor number 'in'we have to check then we will create watchpoint on field LIFNR value '2000'. then we can directly go to vendor whose number is 2000

K.Kiran.

Former Member · ‎11-01-2007

Hi Prashanth,

Check the following link for the ABAP debugger. It is a complete debugger tutorial.

Do award poits if helpful.

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/media/uuid/f720ea47-0801-0010-f7a3-bd37d44fee...

Former Member · ‎11-01-2007

Watchpoints

Summary

Watchpoints allow you the option of monitoring the content of individual variables.

The Debugger stops as soon as the value of the monitored variable changes.

In addition, conditions can be specified. The Debugger also checks whether such a condition is fulfilled.

Detailed Description

Creating a Watchpoint

In the toolbar of the New Debugger, you will find the pushbutton Create Watchpoint . It brings you to the dialog box Create Watchpoint.

Using this function, you can enter the variable to be monitored.

All possible ABAP data structures are allowed here.

-

Special Case: Watchpoint for Internal Table

Setting a watchpoint for an internal table may have a negative effect on performance during program runtime and also cause an increase in memory consumption.

The reason for this is that a “clone” of the original data object is created for the watchpoint on a table (as for every other watch point as well).

If the table for which the watchpoint was set has become too large, you must take into consideration that the "clone" will have the same size. With very large internal tables, this can lead to memory bottlenecks.

In some cases, therefore, it can be a good idea to have watchpoints for internal tables active only for short program durations.

Note

In those cases where you are interested solely in changes to the number of lines in the internal table, you can proceed as follows:

Set a watchpoint for a header in the internal table – for example, ."*ITAB[]", possibly with the condition

Not equal to current number: "LINES( ITAB ) <> 1000"

-

When you create a watchpoint, the variable taken as the default value for the watchpoint is the variable on which the cursor is currently positioned (in the editor or another tool).

You can only set watchpoints for variables of the current context (program).

For local variables, you can specify whether the watchpoint is to apply to the current procedure instance or to all instances that were ever called for this procedure. Particularly for recursive calls of the procedure, this difference can be of importance.

In addition, you can enter any arbitrary condition in the following box “Condition”. Only if the watchpoint variable changes AND the condition is fulfilled will the Debugger stop.

The condition must match the following syntax:

)“.

In the Breakpoints tool (desktop Breakpoints/Watchpoints / Tab Watchpoints), you can view this reached watchpoint in detail.

The reached watchpoint is marked with a yellow arrow. The old and the new values of the watchpoint variable are at your disposal.

In addition, you can use the pushbutton Compare Variables () to determine the differences between the old and the new variable.

In addition, you can maintain the watchpoint in this view – that is change, activate, deactivate, or delete it.

·

Validity Area for Watchpoints

· In contrast to breakpoints, watchpoints are only valid locally in the roll area. If a roll area changes, none of the watchpoints defined in the underlying roll area are visible. Also, watchpoints that were created in the New ABAP Debugger cannot be used further in the Classic Debugger (for example, after changing the Debugger) and vice versa.

Breakpoints

Setting and editing breakpoints, too, in the new Debugger is almost identical to the classic Debugger. However, several breakpoints can be set simultaneously in the new Debugger if you choose the path Breakpoint ® Create Breakpoint. Afterwards, the system displays a window in which the following options are available.

Here it is obvious that, in contrast to the classic Debugger, all the input fields – with the exception of those in the ABAP command tab – have a search help function (function key F4). For example, under the Method tab you enter a certain class. Then, in the search help, all the methods that belong to this class are proposed.

There are also certain differences when setting and deleting breakpoints. A double-click within a source code line creates a breakpoint in this line in both Debugger types, provided the cursor was not positioned on an ABAP keyword. A second double-click in the same line deletes this breakpoint in the classic Debugger, while it is only deactivated in the new Debugger.

Breakpoint Types

When you set a breakpoint in the Debugger, it is created as a debugger breakpoint by default. A debugger breakpoint is only valid while the Debugger instance, in which it was set, is active. When the Debugger is closed, all debugger breakpoints set in it are deleted.

If you set a breakpoint in the ABAP Editor, for example, this breakpoint is a session breakpoint. Session breakpoints remain active independently of the existence of a Debugger and are valid for all external sessions of a logon. Within the Debugger, you can convert a debugger breakpoint into a session breakpoint and vice versa.

If the setting Session Breakpoints Active Immediately is checked (via Utilities ® Settings ® ABAP Editor ® Debugging in the ABAP Editor or Object Navigator), you can set a session breakpoint in an external session of a logon to force a running program into the Debugger that runs in the same logon (for example, in an external session) and will process the point at which the session breakpoint was set.

User breakpoints (previously known as external breakpoints) are valid for all user logons on the current server of the current system. User breakpoints are specifically required when debugging BSP or Web Dynpro applications. In these cases, you do not log on using the SAP GUI but via a browser, for example. Therefore, any breakpoints must be set before logging on.

User breakpoints are only valid for a period of 2 hours.

As of Release 7.00, user breakpoints set for BSP or Web Dynpro applications are also valid for SAP GUI logons.

Within the Debugger, you can convert debugger or session breakpoints into user breakpoints and vice versa.

Rewards if useful...............

Minal