launch.json problems about vscode-perl-debug

[sorinmustaca]

Ah, I found the solution in the other posts...
{
"version": "0.2.0",
"configurations": [

        {
            "type": "perl",
            "request": "launch",
            "exec": "C:\\Perl\\bin\\perl.exe",
            "execArgs": [],
            "name": "Perl-Debug",
            "root": "${workspaceRoot}",
            "program": "${relativeFile}",
            "inc": [],
            "args": [],
            "stopOnEntry": true
        }
    ]

}

[raix]

Hi @sorinmustaca can you give #19 (comment) a go?

I've been preparing a new release the past two weeks improving things just waiting for tests to pass

[sorinmustaca]

Here is the solution:

{
"version": "0.2.0",
"configurations": [

        {
            "type": "perl",
            "request": "launch",
            "exec": "C:\\Perl\\bin\\perl.exe",
            "execArgs": [],
            "name": "Perl-Debug",
            "root": "${workspaceRoot}/",
            "program": "${workspaceRoot}/${relativeFile}",
            "inc": [],
            "args": [],
            "stopOnEntry": true
        }
    ]

}

I can at least start the debugger now :)

However, it is still not working as it should.
The debugger is started in the wrong folder: the folder of the solution, not where the perl source code is.

I have a structure like this:
/

• /f1
• /f2
  -/src -> this is where my code is: test.pl which includes a utils.pm, in the same folder.

I loaded in VSCode the folder from the root.
When I debug, I see that VSCode executes
perl -d src/test.pl
and test.pl fails to find Utils.pm, despite the fact that i use an use lib "./";

After I change the start folder to src/ then it returns this error:
Error
Error: spawn C:\Perl\bin\perl.exe ENOENT

[raix]

@sorinmustaca I've released 0.2.1 this should be solved both in creating proper initial settings for windows users and fixed path resolver internally.

Closing this, but let me know if it's still causing issues