SAP技术专家的ABAP调试器培训材料

首先弄清楚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?

解决方案：使用事务码sbgrfcmon

小技巧2：如何调试update task

小技巧3：如何使用ABAP观察点 Watch point

练习：我们进入事务码SE09时，会观察到User字段会自动被填充成当前登录用户。如何通过观察点快速找到是哪一行代码赋的值？

When we use SE09, how can we find the logic of the User? When and where is this field filled? What does content come from?
Debugging step by step will be very time-consuming.

小技巧4：使用ABAP检查组 Check group

小技巧5：事务码SRDEBUG

小技巧6：调试脚本

要获取更多Jerry的原创文章，请关注公众号"汪子熙":