SAP Eclipse / ADT Debugger does not stop at break point – #ADTsetup #ADTdebugger
currently I suffered the issue that at a customers sandbox system that the Eclipse debugger did not stop at break point when:
- Running console output via F9
- classic reports
- Unit Test
In classic runs via F8 during embedes SAP GUI the eclipse debugger did fire up and does it’s job.
Same source code was running and breaking fine on an other system.
The issue was due to wrong m system Parameter: rfc/ext_debugging
This needs to be set to 3
Keep this in mind during #ADTsetup.
Thanks to Armin Beil Blog I was able to solve this.
ADT ABAP Debugger – What to do if your program does not stop at breakpoints
Hope this is of any help for some of you
I'm happy that my blog was helpful. This parameter problem is actually one of the first things to check. Therefore I just rearranged the list and shifted the parameter problem to a much higher position.
In the newest releases & SPs of the ABAP platform a misconfiguration is not possible anymore. The parameter was completely removed. But it will take some time until there are no more systems with this misconfiguration.