What is an object for the Software Layer Aware Debugging?

[Former Member]

Hi everyone

The reason of this question is that I'm trying to make the debugger stop  at every single custom code include. (very useful to find if any user-exit, badi, etc etc is messing up some process).

I've seen people suggesting you could use the layer aware feature of the debugger with an object set of all Z* packages, but sadly that doesn't work in all cases. It doesn´t work for example in SD-like user exits, where you have a customer include inside an standard function module. Seems like SLAD doesn't recognize that include as an object, but the whole function group instead, and as the function group is created in an standard package the SLAD doesn't stop when entering the Z include.

I find that really annoying and almost a deal breaker for the SLAD, please prove me wrong

[Sandra_Rossi]

Possible objects : program (class pool, report, module pool, etc.) and function module.

I agree that SLAD has limited features, but stopping at all custom code positions is not part of its objectives as you can see in its documentation.

A workaround is to create a debugger script to set breakpoints at all the subroutines you want, and activate SLAD at the same time, so that to addition their features.

[Former Member]

As per documentation: "To debug only the part of the relevant code you are interested in (for example, the code for which you are responsible). "

Maybe it's me misunderstanding that sentence, but I would asume you should be able to do what I wanted to do initially.

Thanks por pinting out the solution of putting breakpoints, sadly is not useful for my purposes, as it would require to know where to put them beforehand, and that is what I was tryng to avoid at first.