When can we expect ABAP debug scripting in Eclipse ?

[phil_soady]

When is the eclipse equivalent of ABAP debug scripting to be delivered ?

[Armin_Beil]

Hi Phil,

debugger scripting in ADT is currently not part of our backlog or roadmap. It is not possible to promise a delivery date.

What are your use cases for scripting? It's interesting for us to know and maybe we can provide a work around proposal.

Thanks and best regards,
Armin

[matt]

Funny that. Although I love using Eclipse for development, for debugging, I always go SAPGui.

[phil_soady]

My requirement happened today, how to view logical Object values not exposed a properties.

If an object doesnt not have a bags of properties and values are only returned via getters only, how can these be viewed in the debugger.

I need to alter the source put test code in to get the values I want to see in the debugger.

My first thought was, classic case for script debugging.

object->getter( )

[Armin_Beil]

Hi Phil,

thanks for the input. I assume the getter method is complex or contains some kind of calculation, correct? ("object doesnt not have a bags of properties")

Actually I think even with scripting this would be hard to solve for you because the getter method must be executed in the context of the debuggee while the script runs in the context of the debugger (different ABAP process). A way to execute ABAP in the context of the debuggee, like some kind of ABAP console during debugging, is also a wish we have but development capacity and priorities didn't allow us to provide such a feature yet.

Best regards,
Armin

[vonglan]

Hi Armin,

With respect to the question: "What are your use cases for scripting?":

I use the Debugger Scripting feature very often (nearly every week) with a script based on an example from Christian Günter here https://github.com/christianguenter2/sitFRA_2016 ->

zrstpda_script_statement_break.prog.abap

that allows to define pattern-breakpoints, e.g.

• "stop whenever a code line with the pattern *vstel* is encountered"

This is a very useful feature to have in Debugging, for example when trying to understand why a BAPI does not behave as expected.

Another script that would be very useful (and that I plan to write when I have time) is:

• "stop at every Z-Code OR modification OR user exit OR enhancement"

Best regards,

Edo

[phil_soady]

yep, lots of reasons to use abap scripting... very powerful .

[Armin_Beil]

Thanks a lot for the input edo!

[ChristianGnter]

Great to hear that you still use the script 🙂 You once sent me your updated version but I forgot to update the github repo. Now I can't find your mail anymore. Can you send me the script again so I can update the repo? Thanks a lot.

Christian

[joachimrees1]

> "stop at every Z-Code OR modification OR user exit OR enhancement"

Yes, sounds indeed very useful!

> You once sent me your updated version but I forgot to update the github repo. Now I can't find your mail anymore.

<joking>

Ah, so this is how github works! ;-))

</joking>

[rpscg]

At about the same time that the TPDA scripting methods are properly documented and explained.
Some of the provided scripts are useful and it is obviously powerful but generally it's a non-intuitive farce if you try to get creative.