Debugger: What am I doing wrong?

[ntreeby]

I am preparing a demo / training project for our developers, who are used to working in Eclipse, who may be interested in migrating to working in VS Code instead.

I have most of the basics covered, with the exception of debugging local code. I cannot figure out how to debug the most basic of procedures. Here is the procedure I am trying to debug:

// main.p
VAR INT i.

ASSIGN i = 1.  // Break point here

MESSAGE "Hello World!" i.

RETURN.

Here is my openedge-project.json:

{
    "name": "progress-vscode-training", // The name of the project
    "version": "1.0", // The project version
    "oeversion": "12.8", // The OpenEdge version; corresponds to ABL runtime in settings.json
    "graphicalMode": true, // true=prowin.exe ; false=_progres.exe
    "charset": "iso-8859-1", // don't change this
    "extraParameters": "-T .oeabl/temp", // specify a temp dir
    // the PROPATH
    "buildPath": [
        { "type": "source", "path": "src" } // "source" entries are scanned for changes
    ],
    "buildDirectory": ".oeabl/build", // directory r-code will be saved to
    // specify db connections, if required
    "dbConnections": [
        {
            "name": "sports",
            "connect": "-db sports2020 -ld sports",
            "schemaFile": "",
            "aliases": [ ]
        }
    ],
    "numThreads": 1 // number of runtime threads to spin up
}

Here is my .vscode/launch.json

{
  "version": "0.2.0",
  "configurations": [
    {
        "name": "Attach to AVM",
        "type": "abl",
        "request": "attach",
        "hostname": "127.0.0.1",
        "mode": "legacy",
        "port": 3099,
        "localRoot": "${workspaceFolder}",
        "pause": true
    }
  ]
}

How do I launch a debugging session that will hit my breakpoint in main.p? I tried adding -debugReady 3099 to the extraParameters property of my openedge-project.json; this results in the debugger attaching to the project AVM and sitting eternally at a WAIT-FOR in thread.p.

What am I missing here?

Thanks.

[PeterJudgeZA]

@ntreeby I think you need a task to launch the debugger. There's a conversation at https://github.com/orgs/vscode-abl/discussions/117 that may be helpful in describing how to do this.

As nice as the debugger interface in VSCode is (object properties for the win), it's IMO too much of a PITA to use and I resort to debugger:initiaite() and debugger:set-break() in my code and deal with Ol' Faithful. I also have issues when debugging code from one project that depends on another in the same workspace (ie application code project and unit test project).

I tried adding -debugReady 3099 to the extraParameters property of my openedge-project.json; this results in the debugger attaching to the project AVM and sitting eternally at a WAIT-FOR in thread.p.

That sounds technically correct although buggy. Other than the LS devs, who needs to attach to (one of) those processes.

[gquerret]

You can follow the workshop instructions: https://wiki.rssw.eu/workshop/09-Debugger
Currently there are known bugs when working with multiple projects with the debugger (debugger not able to open correct source code).