Language Server and Debug Protocol Adapter for Perl

• Language Server

  • Syntax checking

  • Symbols in file

  • Symbols in workspace/directory

  • Goto Definition

  • Find References

  • Call Signatures

  • Supports multiple workspace folders

  • Document and selection formatting via perltidy

  • Run on remote system via ssh

  • Run inside docker container

  • Run inside kubernetes

• Debugger

  • Run, pause, step, next, return

  • Support for coro threads

  • Breakpoints

  • Conditional breakpoints

  • Breakpoints can be set while program runs and for modules not yet loaded

  • Variable view, can switch to every stack frame or coro thread

  • Set variable

  • Watch variable

  • Tooltips with variable values

  • Evaluate perl code in debuggee, in context of every stack frame of coro thread

  • Automatically reload changed Perl modules while debugging

  • Debug multiple perl programs at once

  • Run on remote system via ssh

  • Run inside docker container

  • Run inside kubernetes

You need to install the perl module Perl::LanguageServer to make this extension work, e.g. run cpan Perl::LanguageServer on your target system.

Please make sure to always run the newest version of Perl::LanguageServer as well.

NOTE: Perl::LanguageServer depend on AnyEvent::AIO and Coro. There is a warning that this might not work with newer Perls. It works fine for Perl::LanguageServer. So just confirm the warning and install it.

Perl::LanguageServer depends on other Perl modules. It is a good idea to install most of then with your linux package manager.

e.g. on Debian/Ubuntu run:

sudo apt install libanyevent-perl libclass-refresh-perl libcompiler-lexer-perl \
libdata-dump-perl libio-aio-perl libjson-perl libmoose-perl libpadwalker-perl \
libscalar-list-utils-perl libcoro-perl

sudo cpan Perl::LanguageServer
    

e.g. on Centos 7 run:

sudo yum install perl-App-cpanminus perl-AnyEvent-AIO perl-Coro
sudo cpanm Class::Refresh
sudo cpanm Compiler::Lexer
sudo cpanm Hash::SafeKeys
sudo cpanm Perl::LanguageServer
    

In case any of the above packages are not available for your os version, just leave them out. The cpan command will install missing dependencies. In case the test fails, when running cpan install, you should try to run force install.

This extension contributes the following settings:

• perl.enable: enable/disable this extension

• perl.sshAddr: ip address of remote system

• perl.sshPort: optional, port for ssh to remote system

• perl.sshUser: user for ssh login

• perl.sshCmd: defaults to ssh on unix and plink on windows

• perl.sshWorkspaceRoot: path of the workspace root on remote system

• perl.perlCmd: defaults to perl

• perl.perlArgs: additional arguments passed to the perl interpreter that starts the LanguageServer

• useTaintForSyntaxCheck: if true, use taint mode for syntax check

• perl.sshArgs: optional arguments for ssh

• perl.pathMap: mapping of local to remote paths

• perl.perlInc: array with paths to add to perl library path. This setting is used by the syntax checker and for the debuggee and also for the LanguageServer itself.

• perl.fileFilter: array for filtering perl file, defaults to [.pm,.pl]

• perl.ignoreDirs: directories to ignore, defaults to [.vscode, .git, .svn]

• perl.debugAdapterPort: port to use for connection between vscode and debug adapter inside Perl::LanguageServer.

• perl.debugAdapterPortRange: if debugAdapterPort is in use try ports from debugAdapterPort to debugAdapterPort + debugAdapterPortRange. Default 100.

• perl.showLocalVars: if true, show also local variables in symbol view

• perl.logLevel: Log level 0-2.

• perl.logFile: If set, log output is written to the given logfile, instead of displaying it in the vscode output pane. Log output is always appended. Only use during debugging of LanguageServer itself.

• perl.disableCache: If true, the LanguageServer will not cache the result of parsing source files on disk, so it can be used within readonly directories

• perl.containerCmd: If set Perl::LanguageServer can run inside a container. Options are: 'docker', 'docker-compose', 'kubectl'

• perl.containerArgs: arguments for containerCmd. Varies depending on containerCmd.

• perl.containerMode: To start a new container, set to 'run', to execute inside an existing container set to 'exec'. Note: kubectl only supports 'exec'

• perl.containerName: Image to start or container to exec inside or pod to use

• type: needs to be perl

• request: only launch is supported (this is a restriction of perl itself)

• name: name of this debug configuration

• program: path to perl program to start

• stopOnEntry: if true, program will stop on entry

• args: optional, array or string with arguments for perl program

• env: optional, object with environment settings

• cwd: optional, change working directory before launching the debuggee

• reloadModules: if true, automatically reload changed Perl modules while debugging

• sudoUser: optional, if set run debug process with sudo -u \<sudoUser\>.

• useTaintForDebug: optional, if true run debug process with -T (taint mode).

• containerCmd: If set debugger runs inside a container. Options are: 'docker', 'docker-compose', 'podman', 'kubectl'

• containerArgs: arguments for containerCmd. Varies depending on containerCmd.

• containerMode: To start a new container, set to 'run', to debug inside an existing container set to 'exec'. Note: kubectl only supports 'exec'

• containerName: Image to start or container to exec inside or pod to use

• pathMap: mapping of local to remote paths for this debug session (overwrites global perl.path_map)

If you developing on a remote machine, you can instruct the Perl::LanguageServer to run on that remote machine, so the correct modules etc. are available for syntax check and debugger is started on the remote machine. To do so set sshAddr and sshUser, preferably in your workspace configuration.

Example:

"sshAddr": "10.11.12.13",
"sshUser": "root"

Also set sshWorkspaceRoot, so the local workspace path can be mapped to the remote one.

Example: if your local path is \10.11.12.13\share\path\to\ws and on the remote machine you have /path/to/ws

"sshWorkspaceRoot": "/path/to/ws"

The other possibility is to provide a pathMap. This allows one to having multiple mappings.

Examples:

"perl.pathMap": [
    ["remote uri", "local uri"],
    ["remote uri", "local uri"]
]

"perl.pathMap": [
    [
    "file:///",
    "file:///home/systems/mountpoint/"
    ]
]

You can run the LanguageServer and/or debugger inside a container by setting containerCmd and conatinerName. There are more container options, see above.

.vscode/settings.json

{
    "perl": {
        "enable": true,
        "containerCmd": "docker",
        "containerName": "perl_container",
    }
}

This will start the whole Perl::LanguageServer inside the container. This is espacally helpfull to make syntax check working, if there is a different setup inside and outside the container.

In this case you need to tell the Perl::LanguageServer how to map local paths to paths inside the container. This is done by setting perl.pathMap (see above).

Example:

"perl.pathMap": [
    [
    "file:///path/inside/the/container",
    "file:///local/path/outside/the/container"
    ]
]

It's also possible to run the LanguageServer outside the container and only the debugger inside the container. This is especially helpfull, when the container is not always running, while you are editing. To make only the debugger running inside the container, put containerCmd, conatinerName and pasth_map in your launch.json. You can have different setting for each debug session.

Normaly the arguments for the containerCmd are automatically build. In case you want to use an unsupported containerCmd you need to specifiy apropriate containerArgs.

It is not defined what the current working directory is at the start of a perl program. So Perl::LanguageServer makes no assumptions about it. To solve the problem you can set the directory via cwd configuration parameter in launch.json for debugging.

If you reference a module with a relative path or if you assume that the current working directory is part of the Perl search path, it will not work. Instead set the perl include path to a fixed absolute path. In your settings.json do something like:

"perl.perlInc": [
    "/path/a/lib",
    "/path/b/lib",
    "/path/c/lib",
],
Include path works for syntax check and inside of debugger.
C<perl.perlInc> should be an absolute path.

You need to install the AnyEvent::IO and Coro. Just ignore the warning that it might not work. For Perl::LanguageServer it works fine.

Change port setting from string to integer

Please make sure the path to the module is in perl.perlInc setting and use absolute path names in the perlInc settings or make sure you are running in the expected directory by setting the cwd setting in the lauch.json.

This is not an issue, that just means that not all features of the debugging protocol are implemented. Also it says ERROR, it's just a warning and you can safely ignore it.

Upgrade to Version 2.4.0

This is a problem when more than one instance of Perl::LanguageServer is running. Upgrade to Version 2.4.0 solves this problem.

You can read stdin from a file during debugging. To do so add the following parameter to your launch.json:

"args": [ "<", "/path/to/stdin.txt" ]

e.g.

{ "type": "perl", "request": "launch", "name": "Perl-Debug", "program": "${workspaceFolder}/${relativeFile}", "stopOnEntry": true, "reloadModules": true, "env": { "REQUEST_METHOD": "POST", "CONTENT_TYPE": "application/x-www-form-urlencoded", "CONTENT_LENGTH": 34 } "args": [ "<", "/path/to/stdin.txt" ] }

If you are using Lhttps://metacpan.org/pod/Carton to manage dependencies, add the full path to the Carton lib dir to your workspace settings file at .vscode/settings.json. For example:

{
  "perl.perlInc": ["/home/myusername/projects/myprojectname/local/lib/perl5"]
}

{
  "perl.perlInc": ["/Users/myusername/projects/myprojectname/local/lib/perl5"]
}

Does not yet work on windows, due to issues with reading from stdin. I wasn't able to find a reliable way to do a non-blocking read from stdin on windows. I would be happy, if anyone knows how to do this in Perl.

Anyway, Perl::LanguageServer runs without problems inside of Windows Subsystem for Linux (WSL).

see CHANGELOG.md

• Presentation at German Perl Workshop 2020:

https://github.com/richterger/Perl-LanguageServer/blob/master/docs/Perl-LanguageServer%20und%20Debugger%20f%C3%BCr%20Visual%20Studio%20Code%20u.a.%20Editoren%20-%20Perl%20Workshop%202020.pdf

• Github: https://github.com/richterger/Perl-LanguageServer

• MetaCPAN: https://metacpan.org/release/Perl-LanguageServer

For reporting bugs please use GitHub issues.

This is a Language Server and Debug Protocol Adapter for Perl

It implements the Language Server Protocol which provides syntax-checking, symbol search, etc. Perl to various editors, for example Visual Studio Code or Atom.

https://microsoft.github.io/language-server-protocol/specification

It also implements the Debug Adapter Protocol, which allows debugging with various editors/includes

https://microsoft.github.io/debug-adapter-protocol/overview

To use both with Visual Studio Code, install the extension "perl"

https://marketplace.visualstudio.com/items?itemName=richterger.perl

Any comments and patches are welcome.

Copyright 2018-2022 Gerald Richter.

This program is free software; you can redistribute it and/or modify it under the terms of the Artistic License (2.0). You may obtain a copy of the full license at:

Lhttp://www.perlfoundation.org/artistic_license_2_0

Any use, modification, and distribution of the Standard or Modified Versions is governed by this Artistic License. By using, modifying or distributing the Package, you accept this license. Do not use, modify, or distribute the Package, if you do not accept this license.

If your Modified Version has been derived from a Modified Version made by someone other than you, you are nevertheless required to ensure that your Modified Version complies with the requirements of this license.

This license does not grant you the right to use any trademark, service mark, tradename, or logo of the Copyright Holder.

This license includes the non-exclusive, worldwide, free-of-charge patent license to make, have made, use, offer to sell, sell, import and otherwise transfer the Package with respect to any patent claims licensable by the Copyright Holder that are necessarily infringed by the Package. If you institute patent litigation (including a cross-claim or counterclaim) against any party alleging that the Package constitutes direct or contributory patent infringement, then this Artistic License to you shall terminate on the date that such litigation is filed.

Disclaimer of Warranty: THE PACKAGE IS PROVIDED BY THE COPYRIGHT HOLDER AND CONTRIBUTORS "AS IS' AND WITHOUT ANY EXPRESS OR IMPLIED WARRANTIES. THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT ARE DISCLAIMED TO THE EXTENT PERMITTED BY YOUR LOCAL LAW. UNLESS REQUIRED BY LAW, NO COPYRIGHT HOLDER OR CONTRIBUTOR WILL BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, OR CONSEQUENTIAL DAMAGES ARISING IN ANY WAY OUT OF THE USE OF THE PACKAGE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.