Debug works but only in console

[GitMensch]

Using the following configuration I've got to a "working" state (the debugger is called and I can interact with it - but only in the debug console).

{
    "version": "0.2.0",
    "configurations": [
        {
            "type": "perl",
            "request": "launch",
            "name": "Perl-Debug local",
            "console": "integratedTerminal",
            "program": "${workspaceFolder}/${relativeFile}",
            "exec": "D:\\dev\\MinGW\\msys\\1.0\\bin\\perl.exe",
            "execArgs": [],
            "root": "${workspaceRoot}/",
            "inc": [],
            "args": ["$sampleInput"],
            "env": {},
            "debugRaw": true,
            "debugLog": false,
            "stopOnEntry": true,
            "sessions": "single"
        }
    ]
}

It actually works to set a breakpoint via vscode and to use "Continue (F5)", too.

I guess this is a perl version issue (perl 5.8.8 with perl5db.pl version 1.28), but I specifically needed to debug in this environment (still can do it now via the console, so thank you for this extension already).

Is there something one can do to allow the "real" interaction between the editor and the debugger with this environment?

[dseynhae]

I recall the same problem when using Perl 5.8.8.

But can't you engage with a newer version, just for debugging purposes?

[elrond1999]

I see this also. The debug console works. But no watch call stack etc. Tried perl 5.8.9 and 5.12.5 both behave the same.

[rafoid]

same for me - I'm using VSCode (v1.49.2) on Mac via container debugging. My env starts CentOS 7.5.1804 container and I install PD v0.6.3 into container - GUI doesn't work, only debug console - I have perl v5.16.3 in the container. It wasn't working at all at first - looking through output revealed that I had to install PadWalker - then I was able to interact with PD via debug console only. Any help is appreciated.