Breakpoints in classic debugger

 BREAKPOINTS

A breakpoint is a signal at a particular point in the program that tells the ABAP runtime processor to interrupt processing and start the Debugger. The Debugger is activated when the program reaches this point. 

The Debugger contains different breakpoint variants:

 Static Breakpoints

A user-specific breakpoint is inserted in the source code as an ABAP statement using the keyword BREAK-POINT. A non user-specific breakpoint is set in the ABAP Editor using the BREAK user name statement.

Dynamic Breakpoints 

Can be set in the ABAP Editor or the Debugger by double-clicking a line, for example. Dynamic breakpoints are always user-specific, and are deleted when you log off from the R/3 System.Dynamic breakpoints are more flexible than static breakpoints because you can deactivate or delete them at runtime. They have the following advantages: 

·        You do not have to change the program code. 

·        You can set them even when the program is locked by another programmer.

·        You can define a counter that only activates the breakpoint after it has been reached.

Special dynamic breakpoints are useful when you want to interrupt a program directly before a particular ABAP statement, a subroutine, or an event, but do not know exactly where to find it in the source code. Event here is used to refer to the occurrence of a particular statement, for example, or calling up a method. Special dynamic breakpoints are user-specific. You can only set them in the Debugger. For more information, refer to the chapter Dynamic Breakpoints.

Breakpoints at Statements

  The Debugger stops the program immediately before the specified statement is executed.

Breakpoints at Subroutines

   The Debugger stops the program immediately before the specified subroutine is called.

Breakpoints at Function Module Calls

  The Debugger stops the program immediately before the specified function module is called.

Breakpoints at Methods

    The Debugger stops the program immediately before the specified method is called.

Breakpoints at System Exceptions

   The Debugger stops the program immediately after a system exception, that is, after a runtime error has been intercepted.