combining watchpoints in new abap debugger

[Former Member]

Hi

I know how to create watchpoints . but in old debugger there is an option of GOTO -Control debuggin -> watchpoints

here u can link all the watch points with OR / AND . however there is no such option in the new debugger

how do i link the watchpoints in new debugger

[Former Member]

Hi

I know how to create watchpoints . but in old debugger there is an option of GOTO -Control debuggin -> watchpoints

here u can link all the watch points with OR / AND . however there is no such option in the new debugger

how do i link the watchpoints in new debugger

[Former Member]

Hi,

You can give the conditions in the create watch point option.

You can refer the below link for more information

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

Thanks

Mani

[Former Member]

Hello,

Try this link.. <external link removed>

Message was edited by: Suhas Saha

[Former Member]

i know how to create a watchpoint and also how to specify the condition in the watchpoint

my question is how do i link 2 watchpoints like either Watchpoint 1 OR watchpoint 2 reached then control should stop.

In old debugger there is option of goto - control debugging watchpoints

here u can link all the watch points with OR / AND . however there is no such option in the new debugger

[Former Member]

Is this Snap shot of Old Debugger ?

If yes , then i don't know or else you can you this.

[Former Member]

Hi Hema,

i have posted for the same only for to combine several watch points with AND/OR.

Find the below screen shot

[Former Member]

here u have used a single variable l_opt_list

but can i say l_opt_list-name = 'test' OR sy-index = 5

i mean can we put two different variables in same condition

[Former Member]

Hi Hema,

You can give multiple variables in one single statement like as your requirement.

You can do the R&D On this by changing the variables .

Thanks

Mani

[Former Member]

in debugging mode..CTRL+f10 and then Watch-point tab. and then create as much as you want

[Former Member]

A minor addition to Nagamani's reply.

Old debugger has OR/AND option, which is less flexible.

If you have 5 watchpoints, we can only choose whether control stops on every watchpoint condition, or all the watchpoint conditions.

New debugger has more flexibility, and it can emulate old debugger behavior too.

To know when variable lv_first equals '1' and lv_second equals '2' at the same time (old debugger's AND linking), watchpoint can be set at lv_first variable, and in addition condition, we can write:

lv_first = '1' AND lv_second = '2'

Although watchpoint is at lv_first variable, you are effectively watching both variables.

When compared to old debugger, it allows you to combine some conditions in one watchpoint, and some other set of conditions in another watchpoint.

As compared to 5 watchpoints created in old debugger where AND would link all 5 of them, new debugger allows you to choose which specific watchpoints out of those 5 to link using AND condition.

To compare variables in addition condition of watchpoint, quotes need to be removed as they indicate literal value.

For example, watchpoint on lv_first can have additional condition as:

lv_first = lv_second AND lv_third > lv_fourth

[gunesbt]

Hi ,

It's been long time but I want to ask about the correct answer. I tried the same way for combining 2 watchpoints but it only cares about the one which is written as variable. Let say I created the watchpoint for lv_var1. And the condition is  lv_var1 = x and lv_var2 = y. However, watchpoint is reached immediately after lv_var1 = x.

I tried a lot of irrelevant things like changing the variable as lv_Var2, writing the conditions,equalities,variables etc in quotes but no luck. Therefore I used "condition for breakpoint" as a workaround which works perfectly but it might not be enough for some cases in the future.

[naga_arjun2]

Hi

Try this link http://scn.sap.com/docs/DOC-10254/diff

Regards,

Arjun

[Former Member]

Hi Naga

The link posted by you is actually pointing to version comparison of document.

Correct link would be this: