Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 

Skip breakpoint vs disable ALL breakpoint in ADT

former_member478603
Participant
0 Kudos
994

What's the difference between skip ALL and Disable ALL breakpoints in ADT

1 ACCEPTED SOLUTION

Armin_Beil
Product and Topic Expert
Product and Topic Expert
0 Kudos
931

The 'Skip All Breakpoints' functionality (= breakpoint icons get crossed out) makes all breakpoints non-functional and therefore behaves almost like a main switch for debugging in general. There are different use cases in which developers want to deactivate all debugging for a short time (e.g. for 2 min) and then reactivate it afterwards.

Of course you can achieve the same result by disabling all breakpoints (= breakpoint icons become empty circles) and then re-enabling the relevant breakpoints. But to restore the same state as before your temporary debugging-pause you need to remember which breakpoints were disabled and which breakpoints were enabled before. This is easy for a lot of developers but depends on work-style. Some developers like to keep dozens of breakpoints and never delete them. E.g. some developers actually have permanently like 20 to 100 breakpoints and never delete them. They keep most of them disabled and only enable the breakpoints that they currently want to use. So when having e.g. 50 disabled breakpoints and 5 enabled breakpoints and then wanting to temporarily disable all debugging for just 2 minutes that's when disable-all becomes cumbersome for them and where skip-all is helpful.

PS: Enable/disable breakpoints as well as the skip-all-feature are basic features by the Eclipse IDE and are not ABAP-specific / not provided by the ADT plugins. E.g. if you use Eclipse for Java development with Java breakpoints then it is the same behavior.

2 REPLIES 2

Armin_Beil
Product and Topic Expert
Product and Topic Expert
0 Kudos
932

The 'Skip All Breakpoints' functionality (= breakpoint icons get crossed out) makes all breakpoints non-functional and therefore behaves almost like a main switch for debugging in general. There are different use cases in which developers want to deactivate all debugging for a short time (e.g. for 2 min) and then reactivate it afterwards.

Of course you can achieve the same result by disabling all breakpoints (= breakpoint icons become empty circles) and then re-enabling the relevant breakpoints. But to restore the same state as before your temporary debugging-pause you need to remember which breakpoints were disabled and which breakpoints were enabled before. This is easy for a lot of developers but depends on work-style. Some developers like to keep dozens of breakpoints and never delete them. E.g. some developers actually have permanently like 20 to 100 breakpoints and never delete them. They keep most of them disabled and only enable the breakpoints that they currently want to use. So when having e.g. 50 disabled breakpoints and 5 enabled breakpoints and then wanting to temporarily disable all debugging for just 2 minutes that's when disable-all becomes cumbersome for them and where skip-all is helpful.

PS: Enable/disable breakpoints as well as the skip-all-feature are basic features by the Eclipse IDE and are not ABAP-specific / not provided by the ADT plugins. E.g. if you use Eclipse for Java development with Java breakpoints then it is the same behavior.

0 Kudos
931

Thanks a lot. It was helpful.