Do something extra when debugging

[rosenberg_eitan]

Let assume that we want to do something extra in case of debugging.

I found out that I can use cl_abap_debugger:

DATA: it_breakpoints_complete TYPE breakpoints_complete .

  cl_abap_debugger=>read_breakpoints( IMPORTING  breakpoints_complete = it_breakpoints_complete ) .

  IF it_breakpoints_complete IS NOT INITIAL . 

  * do something extra.....

  ENDIF .

I just add a break point to the program and it is working .

Is there a better way of doing this ?

Thank for any feed back .

[RaymondGiuseppi]

As IF SY-DEBUG IS NOT INITIAL ?

Regards,

Raymond

[rosenberg_eitan]

Thanks .

I will check.

Regards.

[rosenberg_eitan]

Hi,

What needs to be done so the system will put something in SY-DEBUG ?

Regards.

[Former Member]

DEBUG is internal use, can`t be read in ABAP program. I like your solution.

Regards,
Archer

[rosenberg_eitan]

Thanks.

I found about it only this morning and I like to know if someone has tried it in production system .

I want to reduce the chance of potential problems if I can.

Regards.

[Clemenss]

Hi,

will it find hard-coded or 'soft' session break points?

Regards,

Clemens

[rosenberg_eitan]

Hi,

This is my only  test :

Regards.

Code:

*&---------------------------------------------------------------------*

REPORT z_r_eitan_test_30_01.

INITIALIZATION.

  PERFORM at_initialization .

*----------------------------------------------------------------------*

FORM at_initialization .

  DATA: it_breakpoints_complete TYPE breakpoints_complete .

  cl_abap_debugger=>read_breakpoints( IMPORTING  breakpoints_complete = it_breakpoints_complete ) .

  IF it_breakpoints_complete IS NOT INITIAL .

  ENDIF .

ENDFORM .

*----------------------------------------------------------------------*

[Former Member]

both will return value from that method. i just test it.

regards,

Archer