About watch points and break points...

Hi ,
How many watchpoints and breakpoints can be used in each program?

Hi Eswanth,
I think at a maximum of 30 breakpoints can be used in a program.
Are you going to appear for a sap certification exam or what .
All the best .
Reward if useful.
Regards,
Muneesh Gitta.

Similar Messages

Watch Point

Hi Experts,
Can any one explain me about Watch Points ?
What are the differences between debugger and watch points ?
Can any one explain me how to use watch points with any sample program, if provided with screen shots. I will give full points if any one explain with sample program with screen shots.
Pls send me to [email protected]
Thanks in Advance
Regards and Thanks
Vijaya

Hi vijaya,
check the below links for watch points
Setting Watchpoints
http://help.sap.com/saphelp_erp2005/helpdata/en/c6/617cdce68c11d2b2ab080009b43351/frameset.htm
Changing Watchpoints
http://help.sap.com/saphelp_erp2005/helpdata/en/c6/617ce2e68c11d2b2ab080009b43351/frameset.htm
Watchpoint with the new debugger 5.0
Go through these threads for more information on debugging,
1) debugging
2) debugging
3) Debugging
4) Debugging
some more links .....
Introduction: http://www.saplinks.net/index.php?option=com_content&task=view&id=24&Itemid=34
A PDF file to know knowledge about Debugging
Some more links:
http://www.sap-basis-abap.com/sapab002.htm
Debug Background Programs: http://www.sapdevelopment.co.uk/tips/debug/debug_backjob.htm
Debugger: http://help.sap.com/saphelp_nw2004s/helpdata/en/c6/617ca9e68c11d2b2ab080009b43351/content.htm
If you need futher information plz do let me know
~~Guduri

Types of watch points and break points

hi to all
what are the different types of watch points and break points

Hi Mahesh!
Breakpoints
In the Breakpoints area, you will see a list of all the breakpoints set so far. If one of the breakpoints has just been reached, this is marked with a yellow arrow. The visibility (Debugger, session, user) and type (line, ABAP command, u2026) is displayed for each breakpoint.
If you double click the Navigation() column, the system will display the breakpoint in the respective source code.
The visibility of a breakpoint can be changed through the dropdown list. To change the visibility of several breakpoints, mark them and select the pushbutton Save as Session Breakpoint or Save as User Breakpoint.
You can change the visibility of all Debugger breakpoints using the menu path Breakpoints-> Save Debugger BPs as -> ....
In addition, you have functions for creating, changing, activating and deactivating breakpoints at your disposal.
Watchpoints
In the Watchpoints area, you will see a list of all the watchpoints set so far. The watchpoint last set is highlighted with a yellow arrow.
For each watchpoint you will see not only the current value but the value before the last changed. (Technically speaking, each time you create the watchpoint and each time the watchpoint variable is changed, a clone of this variable is created.)
In this way, you can always determine what changes have been made to the monitored variable. For complicated data structures, such as internal tables or structures, select the pushbutton u201ECompare Variablesu201C( ) and choose the Diff tool to compare the old and new variable values.
In addition, you have functions for creating, changing, activating and deactivating watchpoints at your disposal.
For details
http://help.sap.com/saphelp_nw70/helpdata/en/e2/5f5a42ed221253e10000000a155106/content.htm
Reward points if helpful.

What is the utility of watch point and break point in ABAP DEBUGGING !

What is the utility of watch point and break point in ABAP DEBUGGING !
PLEASE TELL ME IN DETAILS AND IF POSSIBLE WITH SCREEN SHOTS !

Hi,
Breakpoints, Watchpoints, and Checkpoints
Summary
The standard Breakpoints tool is always located on the Breakpoints desktop. With this tool, you can manage breakpoints, watchpoints and checkpoints. In addition, you can monitor the current status of the different breakpoint types.
Detailed Description
Breakpoints
In the Breakpoints area, you will see a list of all the breakpoints set so far. If one of the breakpoints has just been reached, this is marked with a yellow arrow. The visibility (Debugger, session, user) and type (line, ABAP command, ) is displayed for each breakpoint.
If you double click the Navigation() column, the system will display the breakpoint in the respective source code.
The visibility of a breakpoint can be changed through the dropdown list. To change the visibility of several breakpoints, mark them and select the pushbutton Save as Session Breakpoint or Save as User Breakpoint.
You can change the visibility of all Debugger breakpoints using the menu path Breakpoints-> Save Debugger BPs as -> ....
In addition, you have functions for creating, changing, activating and deactivating breakpoints at your disposal.
Watchpoints
In the Watchpoints area, you will see a list of all the watchpoints set so far. The watchpoint last set is highlighted with a yellow arrow.
For each watchpoint you will see not only the current value but the value before the last changed. (Technically speaking, each time you create the watchpoint and each time the watchpoint variable is changed, a clone of this variable is created.)
In this way, you can always determine what changes have been made to the monitored variable. For complicated data structures, such as internal tables or structures, select the pushbutton Compare Variables( ) and choose the Diff tool to compare the old and new variable values.
In addition, you have functions for creating, changing, activating and deactivating watchpoints at your disposal.
Checkpoints
In addition, you can edit conditional and unconditional checkpoints using the Breakpoints tool. This function is provided in the new Debugger only. Conditional checkpoints are set first in the source code using the ASSERTstatement; unconditional checkpoints are set using the BREAK-POINT statement. These have the effect that programs will be continued only if a preset condition is fulfilled. In the following window, these checkpoints can be searched for, activated, or deactivated.
Pls refer to :
http://help.sap.com/saphelp_nw70/helpdata/en/e2/5f5a42ed221253e10000000a155106/frameset.htm
Regards,
Renjith Michael.

What is utility of watch points and break point in ABAp debugging !

What is utility of watch points and break point in ABAp debugging !

Hi,
Breakpoints, Watchpoints, and Checkpoints
Summary
The standard Breakpoints tool is always located on the Breakpoints desktop. With this tool, you can manage breakpoints, watchpoints and checkpoints. In addition, you can monitor the current status of the different breakpoint types.
Detailed Description
Breakpoints
In the Breakpoints area, you will see a list of all the breakpoints set so far. If one of the breakpoints has just been reached, this is marked with a yellow arrow. The visibility (Debugger, session, user) and type (line, ABAP command, ) is displayed for each breakpoint.
If you double click the Navigation() column, the system will display the breakpoint in the respective source code.
The visibility of a breakpoint can be changed through the dropdown list. To change the visibility of several breakpoints, mark them and select the pushbutton Save as Session Breakpoint or Save as User Breakpoint.
You can change the visibility of all Debugger breakpoints using the menu path Breakpoints-> Save Debugger BPs as -> ....
In addition, you have functions for creating, changing, activating and deactivating breakpoints at your disposal.
Watchpoints
In the Watchpoints area, you will see a list of all the watchpoints set so far. The watchpoint last set is highlighted with a yellow arrow.
For each watchpoint you will see not only the current value but the value before the last changed. (Technically speaking, each time you create the watchpoint and each time the watchpoint variable is changed, a clone of this variable is created.)
In this way, you can always determine what changes have been made to the monitored variable. For complicated data structures, such as internal tables or structures, select the pushbutton Compare Variables( ) and choose the Diff tool to compare the old and new variable values.
In addition, you have functions for creating, changing, activating and deactivating watchpoints at your disposal.
Checkpoints
In addition, you can edit conditional and unconditional checkpoints using the Breakpoints tool. This function is provided in the new Debugger only. Conditional checkpoints are set first in the source code using the ASSERTstatement; unconditional checkpoints are set using the BREAK-POINT statement. These have the effect that programs will be continued only if a preset condition is fulfilled. In the following window, these checkpoints can be searched for, activated, or deactivated.
Regards,
Renjith Michael.

What is watch point and break points?what are there types?

what is watch point and break points?what are there types?

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.
Watch point are used to put logical break point for a certain condition..Example..If you want to know when the internal table is getting append..Then you have to give the program name and the internal table in the watch point..
Steps to create a watch point.
Start debugging '/H'.
In the debugging screen press the create watch point button in the application tool bar..
In the program give the program name..
in the field give the field name.
In the relational operator given '='
In the comp. field/value give the value ..
Hope this helps..
Regards,
Parvez.

Break points and watch points

Hi all
 Can anybody help me using break points and watch points.what do they exactly do as well..
Thanks
abap user

Hi
Breakpoints
Instead of starting an ABAP program directly in the Debugger, you can also debug a program by creating one or more 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 program runs normally until the breakpoint is reached.
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 further information, refer to Watchpoints.
Breakpoint Variants
The Debugger contains different breakpoint variants:
Static The BREAK-POINT statement in an ABAP program. Static breakpoints are not normally user-specific. However, you can make them user-specific.
Directly-set
dynamic breakpoints Can be set in the ABAP Editor or the Debugger. Dynamic breakpoints are always user-specific, and are deleted when you log off from the R/3 System.
Breakpoint
at statement The Debugger stops the program directly before the specified statement is executed.
Breakpoint at subroutine The Debugger stops the program directly before the specified subroutine is called.
Breakpoint at function module The Debugger stops the program directly before the specified function module is called.
Breakpoint at method The Debugger stops the program directly before the specified method is called.
Breakpoints at system exceptions The Debugger stops the program directly after a system exception, that is, after a runtime error has been intercepted.
Use
Static Breakpoints
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. You should set static breakpoints whenever more than one programmer is working on the same program and you always want to stop the program in the same place.
Dynamic Breakpoints
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.
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 (for example, only activate the breakpoint after it has been reached five times).
Special Dynamic Breakpoints
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 program 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.
Transferring Breakpoints to HTTP and Update Sessions
If an HTTP or update session is called from a Logical Unit of Work (LUW), new work processes are started for these new sessions. Breakpoints that were defined beforehand in the calling LUW are copied to these sessions where they can be displayed under breakpoints.
If, for example, the update module func is called via CALL FUNCTION func IN UPDATE TASK, the new work process is displayed in a second window if Update debugging was selected under Settings in the debugging mode. All the breakpoints that were set in the calling LUW can then be processed here.
Static Breakpoints
You should only use static breakpoints during the development phase of an application. You must remove them from your program before you transport it.
Setting Breakpoints
To set a static breakpoint, use the ABAP statement BREAK-POINT . Place the breakpoint in the line at which you want to interrupt the program.
program RSDEBUG_01.
if SY-SUBRC <> 0.
break-point.
endif.
When you run the program, the runtime processor interrupts it when the breakpoints occur. You can number your breakpoints to make them easier to identify ( BREAK-POINT 1, BREAK-POINT 2 ).
Static breakpoints are not normally user-specific. The program is, therefore, always interrupted as soon as the runtime processor reaches the line containing the breakpoint. The program is interrupted regardless of the user who executes it.
However, you can set user-specific static breakpoints using the BREAK statement followed by your user name. For example, if you use the statement BREAK SMITH , the program is only interrupted when user Smith runs it. Although user-specific breakpoints appear in the program code, they are not active when other users run the program. You should, however, be careful if an application is being used by several users with the same name.
Deleting Breakpoints
Since static breakpoints apply to all users, you must remove them from the program once you have finished testing it. In the ABAP Editor, you can find breakpoints quickly by choosing Utilities  Global search. You can also use the Extended Program Check to find them.
If you do not remove static breakpoints from your program, they will be transported to your production system. This could cause serious problems in the production system.
Dynamic Breakpoints
You can set up to 30 dynamic breakpoints without changing the program code. Dynamic breakpoints can be set either in the ABAP Editor or directly in the Debugger.
Setting Dynamic Breakpoints in the ABAP Editor
You can set dynamic breakpoints in the ABAP Editor regardless of whether you are in display or change mode. You can also set breakpoints directly from within the Debugger at runtime. To set a dynamic breakpoint in the ABAP Editor:
1. Position the cursor on the line of the source code at which you want to set the breakpoint.
2. Choose Utilities  Breakpoints  Set or the Stop icon. The system confirms that the breakpoint has been set.
To display a list of all dynamic breakpoints in a program, choose Utilities  Breakpoints  Display. You can use this list to navigate to a particular breakpoint or to delete one or more breakpoints from the program.
Setting Dynamic Breakpoints in Debugging Mode
To set a dynamic breakpoint in the Debugger:
1. Position the cursor on the line in which you want to set the breakpoint.
2. Select the line by double-clicking it or choosing Breakpoint  Set/delete.
The system sets the breakpoint, and displays a small stop sign to the left of the relevant line. If the line already contained a breakpoint, it is deleted.
When you finish your debugging session, the breakpoint is automatically deleted unless you have explicitly saved it.

Breakpoints at Statements
You can use this special kind of dynamic breakpoint to interrupt a program directly before an ABAP statement is processed.
Prerequisites
You must already be running the program in the Debugger.
Procedure
To set a breakpoint at an ABAP statement:
1. Choose Breakpoint  Breakpoint at  Statement...
2. Enter the ABAP statement.
The system sets a breakpoint at all points in the program at which the ABAP statement occurs.
3. Choose ENTER.
The breakpoint applies to all lines containing the specified statement.
Result
The system confirms the breakpoint and adds it to the list in the display. When you finish your debugging session, the breakpoint is automatically deleted unless you have explicitly saved it.
Breakpoints at Subroutines
You can use this special kind of dynamic breakpoint to interrupt a program directly before a subroutine is called.
Prerequisites
You must already be running the program in the Debugger.
Procedure
To set a breakpoint for a subroutine:
1. Choose Breakpoint  Breakpoint at  Event/Subroutine.
2. Enter the name of the subroutine before which you want to interrupt the program. By default, the Program field contains the name of the program that is currently active. The system sets a breakpoint wherever the specified subroutine occurs in the program code.
3. Choose ENTER.
Result
The system confirms the breakpoint. The breakpoint is added to the breakpoints displayed.
Breakpoints at Function Module
You can use this kind of dynamic breakpoint to interrupt a program directly before a function module is called.
Prerequisites
You must already be running the program in the Debugger.
Procedure
To set a breakpoint for a function module:
1. Choose Breakpoint  Breakpoint at  Function module...
2. Enter the name of the function module before which you want to interrupt the program. The system sets a breakpoint wherever the specified event, module pool, or subroutine occurs in the program code.
3. Choose ENTER.
Result
If you entered a valid function module name, the system confirms that the breakpoint has been set. If the function module exists in the system, the new breakpoint is added to the display list.
Breakpoints at System Exceptions
You can use this special form of dynamic breakpoint to interrupt a program immediately after a runtime error has occurred.
Prerequisites
You must already be running the program in the Debugger.
Procedure
To set a breakpoint at a system exception:
Choose Breakpoint  Breakpoint at  System exception.
Result
The system confirms the breakpoint. The breakpoint is added to the breakpoints displayed.
When a system exception is triggered, a warning triangle appears in the line containing the statement that caused it. If you double-click the warning triangle, the internal name of the runtime error appears.
Saving Breakpoints
If you want to leave the Debugger temporarily, you can save your dynamic breakpoints so that they are still active when you return to the Debugger within the same terminal session.
To save the breakpoints that you have set in the Debugger:
Choose Breakpoint  Save.
The system saves all of the breakpoints that you have set in the current program. These breakpoints will remain active until you either explicitly delete them or log off from the system.
You can also delete breakpoints that you have saved:
 By deleting individual breakpoints from the display and then saving again. In this case, only your selected breakpoints will be deleted.
 By choosing Breakpoint  Delete all. In this case, the system deletes all dynamic breakpoints.
Managing Dynamic Breakpoints
The ABAP Debugger provides a convenient user interface for managing breakpoints. To open the breakpoint display, choose Breakpoints, or, from the menu, Goto  Control debugging  Breakpoints.
Functions
This display mode contains the following functions for breakpoints:
Breakpoint Display
The scrollable breakpoint display contains up to 30 dynamic breakpoints. For breakpoints that you set directly, the program name and line number at which the breakpoint occurs are displayed. For special breakpoint forms, the list displays the statements, events, subroutines, and module calls at which the relevant breakpoints are set.
Counter
In the breakpoint display, you can specify a counter. When you use a counter, the breakpoint is not activated until it has been reached a specified number of times. For example, if you enter 5 for the counter, the breakpoint is not activated until it is reached for the fifth time. After the breakpoint has been activated, it remains so, and the counter no longer appears in the breakpoint display.
Deleting Breakpoints
Position the cursor on the breakpoint that you want to delete, and either double-click the line or choose Breakpoint  Set/delete. To delete all breakpoints, choose Breakpoint  Delete all.
Activating and Deactivating Breakpoints
Position the cursor on the breakpoint that you want to activate or deactivate and choose Breakpoint  Activate/deactivate.
Watchpoints
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.
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.
 You can also specify the conditions on which a watchpoint is to become active.
 You can specify logical conditions between up to five conditional watchpoints.
 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.
Setting Watchpoints
If you want to interrupt a program when the contents of a field or structure change, use a watchpoint. You can set up to five watchpoints, including watchpoints for strings.
A watchpoint can be either local or global. Local watchpoints are only valid in the specified program. Global watchpoints are valid in the specified program, and also in all the other programs it calls.
Procedure
To set a watchpoint, start the Debugger and proceed as follows:
1. Choose Breakpoint  Create watchpoint or the corresponding pushbutton. The Create Watchpoint dialog box appears.
2. Decide whether you want to set a local or global watchpoint.
3. Enter the program and the name of the field for which you want to set the watchpoint. In the Program field, the name of the program currently running is always defaulted.
4. If you want your watchpoint to be activated each time the contents of the field change, the definition is now complete, and you can return to the Debugger by pressing ENTER .
5. To create a conditional watchpoint, that is only activated when a particular situation arises, choose one of the following relational operators.
Operator Meaning
< Less than
<= Less than or equal
= Equal
<> Not equal
>= Greater than or equal
> Greater than
6.
7. You can use the Comparison field option to specify whether the comparison is to be carried out with a value that you specify or with the contents of another field. Depending on your choice from step 6, enter a value or a field for the comparison.
Result
The system confirms the watchpoint and adds it to the list in the display. When you finish your debugging session, the watchpoint is automatically deleted unless you have explicitly saved it.
Specifying Logical Links
If you have more than one conditional watchpoint, you can specify a logical link between them:
OR Only one of the specified conditions must be met
AND All of the conditions must be met.
To create a logical link between watchpoints:
1. Choose Goto  Control debugging  Watchpoints or the Watchpoints pushbutton to open the watchpoint display.
2. Set the Logical operator between watchpoints option.
The default value is always OR .
Changing Watchpoints
1. Choose Goto  Control debugging  Watchpoints or the Watchpoints pushbutton to display the watchpoint list.
2. Choose the pencil icon in the line containing the watchpoint you want to change.
3. Change the watchpoint attributes in the Create/Change Watchpoint.
3. Choose ENTER .
Deleting Watchpoints
You cannot delete watchpoints by choosing Breakpoint  Delete or Breakpoint  Deactivate/activate. Instead, proceed as follows:
1. Choose Goto  Control debugging  Watchpoints or the Watchpoints pushbutton to display the watchpoint list.
2. Choose the trashcan icon in the line containing the watchpoint you want to delete.
Memory Monitoring with Watchpoints
You can use watchpoints to display changes to the references of strings, data and object references, and internal tables. By placing an ampersand (&) in front of the object name, you can display the reference in question in hexadecimal format. With internal tables, you can also display the table header by placing an asterisk (*) at the beginning of the name.
Reward ifusefull

How to create watch points in ECC 6.0

Hi Experts,
How to create watch points in ECC 6.0
Thanks.

Dear Kalyan,
The moment the debugger starts, there will be an icon for "Watchpoint" exactly after F5, F6, F7, F8 and a big STOP red button on the application tool bar. Once you click on that Watchpoint button, it will take you to the screen where you need to define the exact field and its relative operator along with the condition to be checked.
Hope this is clear. No navigation needed for this.
-Syed.

Regarding watch points in ABAP debugger

Hi,
Could u explain , why we use watch points, what is the use of it
and how to use it.
Thanks & regards,
[email protected]

Watch points
http://help.sap.com/saphelp_nw04/helpdata/en/c6/617cdce68c11d2b2ab080009b43351/content.htm
http://help.sap.com/saphelp_47x200/helpdata/en/14/6d1c370c468b7be10000009b38f936/frameset.htm
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.
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 Setting Watchpoints.
You can also specify the conditions on which a watchpoint is to become active.
You can specify logical conditions between up to five conditional watchpoints.
See Specifying a Logical Expression.
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
If you want to interrupt a program when the contents of a field or structure change, use a watchpoint. You can set up to five watchpoints, including watchpoints for strings.
A watchpoint can be either local or global. Local watchpoints are only valid in the specified program. Global watchpoints are valid in the specified program, and also in all the other programs it calls.
Procedure
To set a watchpoint, start the Debugger and proceed as follows:
Choose Breakpoint ® Create watchpoint or the corresponding pushbutton. The Create Watchpoint dialog box appears:
ashish
Message was edited by:
Ashish Gundawar

Watch points

Hi all,
I know that there are two ways of debugging in ABAP. One is setting the breakpoints and the other is watchpoint.Can anyone please explain me what is watch point, what is the need of going for that when we have debugging option, And how to work with watch point ? what is the difference between local and global watch point.
Regards,
Varun.

Hi Varun,
watch points are used explicitly to stop for a particular record with some value.
say i have 10000 records , i am looping that itab, i cannot say F5 , to see for a particular record, in that case we will create watch point on itab-field which is equal to some value , when you say F8, then it will stay exactly that particular record.
it will save the debugging time.
for more info read this SAP help ..
http://help.sap.com/saphelp_webas610/helpdata/en/c6/617ce2e68c11d2b2ab080009b43351/content.htm
regards
vijay

Watch point on a special field

Hi All,
I have got an exited idea, but when I try to do it, I have problem. The idea is to set watch point on special field SY-REPID. And the watch point condition is SY-REPID = <Program_Name_I_Want_to_step_In>. But I fail to set watch point to the field sy-repid. Othewise we can step into whatever program we want to step in so that we can set watch point to any variable of that program.

You can set a watch point on something like sy-subrc and it will stop whenever the value changes in any program that is called.
(But this won't work with sy-repid, because you cannot set a watchpoint on it. Try setting a watchpoint on SY-XPROG instead.)
Rob
Edited by: Rob Burbank on Oct 26, 2009 10:53 AM

Gripe about the points system...

To whom it may concern,
I have a gripe about the points system used on the forums.Let me start by saying I like the general premise the points system offers but... I have noticed that I certain cases I will receive SEVERAL equally good, helpful, and valid replies to a post. My gripe is that when it comes time to award points I see a problem. In the above scenario AT LEAST one posts MUST get solved points while the others only get helpful points. I don't like this as oft times I believe EVERY answer deserves equal points. I would like to see the system at least allow for all posters to receive helpful points. I feel that in some cases this would keep things fair. Thank you.
Chris
G4 466 Digital Audio 1.5 gB RAM 30 GB HD Mac OS X (10.4.6) Pioneer DVR-111DBK

Thanks for the chance to vent!
Cheers,
Chris

Reminder on forum pages about awarding points?

This isn't for me, since at this rate I will be a Level 4 in something over 600 years, but I was wondering if there could be some kind of discreet and short (clutter avoiding) but highly visible, reminder or announcement on the forum pages, themselves, about awarding points and the points system.
I realize that for most helpers here the satisfaction of helping someone, and maybe even getting a thank you, is enough, but a thank you can be made more meaningful with very little effort.
Many new members are oblivious, don't bother to read the Help and TOU, at least not very carefully, myself included when I first registered here. I see so many not bothering to award points I think, not out of indifference, but simply because they aren't paying attention. Often a question will be marked answered, but no points awarded - not simply to close off the thread, as in some cases - but when there has, in fact, been a genuine solution.
Could there be some form of gentle reminder, avoiding pushiness, at the top of each of the pages? I know there is already the "Solved and Helpful still available" in the actual thread, (and "Answered question, Unanswered question with answer points still available Unanswered question at the bottom of the page"), but I think for many who haven't understood the points system to begin with, these may not even register- or be very noticeable.
If this has already been discussed and dismissed please excuse.

Eric W wrote
We are looking at changes in the future to make it clearer to everyone (new and older users alike) on how the system works.
Thanks Eric; could this include, possibly, some sort of simple notice at the top of the forum pages (as described above, discreet, non-pushy, non-manipulative and, short)? I don't see how this would violate "other forms of encouragement are frowned upon." It would seem to me Apple has everything to gain by creating a more "encouraging" climate for helpers to do their work here. As it is, it must be somewhat frustrating at times.
A Brody wrote
Come in here more often if you feel you have the knowledge of how to offer the best answers.
I'm not sure what this is supposed to mean. With respect, A Brody, am I detecting some needless sarcasm, or am I misunderstanding? I certainly don't presume to offer the "best answers." Is making a simple suggestion presumptuous of me?
You can lead a horse to water, but you can't make them drink.
Agreed. But I wonder if the horse even knows the water is nearby.
People come in here with varying levels of free time. You can't expect everyone to be able to spare the time to mark a thread one way or another.
How much extra time does it take to mark a thread one way or the other? Wouldn't many more people do this only if they were made more aware?
Everyone would and should carefully read the lengthy Help and TOU. But human nature being what it is, most people, especially people interested in finding an answer to a more or less urgent question. are not going to take the time for that. They might, however, pay attention to a short notice.

I have just started with apple tv. I rented and downloaded a movie from itunes on my macbook pro and tried to watch it. I got the movie up, but it only played a picture for about 3 seconds and then stopped, also no sound? What am I doing wrong?

Please help me play a rented itunes video on apple tv. Have a pictue and movie runs for about three seconds, and then stops. No sound? But I can play any music from my library with sound?

Is the movie still buffering? you may have a slow internet connection. Music files require far less bandwidth than movies.

HT4528 Sound from the built-in speaker badly cracks and breaks

Hi, I need a help on trying to figure out what's wrong with my iPhone 4..
I've had my iPhone for about a year, without any major issue. But recently I noticed that the sound coming from the built-in speaker cracks and breaks to a point it barely makes any proper sound. The weird thing is that this happens only for alarm, text/phone ringtones, and during calls when I try to use the speaker.
At first I suspected it was the hardware issue, but when I play music it works just fine. I tried restoring the phone, but that didn't fix the problem.
I'm thinking about taking it to Apple store or Verizon, but my Apple warranty seems to have expired and I don't know what Verizon can do to help. I should still have the protection plan through Verizon, but it doesn't cover much.

f1ght4fun wrote:
Unfortunately, I'm from Cyprus, Europe and diffenrence in time + no Apple Reps here makes it quite hard. I was hoping these threads are also monitored or here might be somebody who knows how to help me.
Either way tnx 4 advice!
This is from the Apple Support Communities Use Agreement:
Apple involvement. Apple does not formally provide technical support on the Site. However, any information that is provided by Apple or Apple employees is offered on an “AS IS” basis without warranties of any kind.
Here is the link: https://discussions.apple.com/static/apple/tutorial/tou.html
Don't get discouraged so easily though, this question hasn't even been up for a full day yet. Give others time to see it

About watch points and break points...

Similar Messages

Maybe you are looking for