SAP技術專家的ABAP偵錯程式培訓材料

SAP · 發表 2019-01-31 13:50:01

摘要：首先弄清楚ABAP Classic偵錯程式和新偵錯程式的區別： Classic debugger: (1) Static breakpoint a. BREAK-POINT : non-user specific b. BREAK user name user s...

首先弄清楚ABAP Classic偵錯程式和新偵錯程式的區別：

Classic debugger:

(1) Static breakpoint

a. BREAK-POINT : non-user specific

b. BREAK user name user specific

(2) Dynamic breakpoint

New debugger:

(1）Static breakpoint

(2）Dynamic breakpoint

a. session breakpoint

b. external breakpoint

Session 斷點和External斷點的區別

(1) Session BP is only visible in all external sessions belonging to the same user session, while External BP is visible across all user sessions. Therefore, only External BP is valid for BSP / Webdynpro debugging.

(2) When a user logs off, Session BP will be deleted while external BP persists.

By setting this flag, if external session A is running, and in external session B ( A and B belongs to the same user session ) you set a session breakpoint in the program source code, the BP will be triggered immediately .

ABAP獨佔斷點(Exclusive Breakpoint)和非獨佔斷點的區別

下圖是非獨佔斷點：

下圖是獨佔斷點：

Exclusive mode means the application to be analyzed exclusively occupies a work process of the application server during debugging. If all exclusive debug work processes are occupied, the Debugger is switched to non-exclusive mode. (rdisp/wpdbug_max_no )

Limitation for non-exclusive mode:

Due to technical limitations in ABAP debugger implementation, there are following limitations when debugger is run under non-exclusive mode:

(1) No possible to debug statement between SELECT and ENDSELECT. In this case, program terminates with this error:

(2) No possible for conversion / field exit.

(3) No possible for debugging in production system, program terminates with exception DEBUGGING_NOT_POSSIBLE.

ABAP偵錯程式裡的一些指標該如何閱讀？

考慮下面這段最簡單的ABAP程式碼：

偵錯程式裡檢視A1這個型別為內表的變數：這裡的[2×1(8)]是什麼意思？

2: table row number

1: table column number

8: byte length of table row

The time for which the new Debugger is active is determined by the profile parameter rdisp/max_debug_lazy_time – which is set to 600 seconds in the standard version. After this time space has elapsed, the Debugger process is exited automatically and control is passed back to the application.

一些小技巧：how to debug background RFC?