Feature #11985
implement the DEBUGGER system handle on top of the 4GL DAP server
Status:
New
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
Due date:
% Done:
0%
billable:
No
vendor_id:
GCD
case_num:
version_reported:
version_resolved:
reviewer:
production:
No
env_name:
topics:
Related issues
History
#1 Updated by Paula Păstrăguș about 10 hours ago
In OpenEdge, 4GL code can drive the debugger through the DEBUGGER system handle:
| Member | What it does in OpenEdge |
|---|---|
VISIBLE |
Shows or hides the debugger window |
INITIATE() |
Initializes the debugger for the session |
DEBUG() |
Starts the debugger and stops at the next executable statement |
SET-BREAK(...) |
Sets a breakpoint |
CANCEL-BREAK(...) |
Removes a breakpoint |
CLEAR() |
Ends the debugger and removes its breakpoints |
DISPLAY-MESSAGE(msg) |
Shows a message in the debugger |
FWD has the handle (com.goldencode.p2j.util.Debugger, DebuggerResource), but every method is a no-op that returns FALSE. Converted code that uses the handle compiles and runs, but nothing happens.
#2 Updated by Paula Păstrăguș about 10 hours ago
- Related to Feature #11742: implement a fully featured Debug Adapter Protocol (DAP) server for 4GL code (in FWD) added