VS Code debug feature not working on Centos

[TrevorBarry]

Hi,

I'm running the following

• Centos 7.6.1810
• VS Code 1.30.1
• Perl 5.16.3
• PadWalker 2.3

I'm using the default launch.json.

When I try to debug a pl file I get the same behavior that was reported in issue 31 (https://github.com/raix/vscode-perl-debug/issues/31) .

If I open the debugger console I can see that my breakpoints are being hit but the VS Code debugger windows don't show anything. Variables, Watch, and Call Stack are always blank. In addition pressing buttons on the debugger toolbar does nothing. I have to interact directly with the debugger via the console to debug stuff.

Is there anything I can do to diagnose/fix this?

Trevor

[yulivee]

Hi, I am encountering the exact same issue. I use the same launch file as TrevorBarry.

• Ubuntu 16.04
• VS Code 1.30.1
• Perl 5.22.1
• PadWalker 2.3

Loading DB routines from perl5db.pl version 1.49
main::(-e:1):   0
  DB<1> print $DB::OUT eval { require PadWalker; PadWalker->VERSION() }
2.3

Variable view says "PadWalker not installed"

[raix]

hmm - it might be related to the padwalker version 2.3 (that's the only thing you have in common - except vs code - but vs code should behave consistently)

[raix]

Actually we use padwalker 2.3 in the linux part of the test matrix - we test alot of perl versions (due to inconsistencies in the distributions) https://github.com/raix/vscode-perl-debug#stability Maybe try upgrading perl?

[bmakan]

Any update on this? I even upgraded the perl. Didn't help. Cannot step through the code, inspect variables, etc.

VS Code: 1.34 PadWalker: 2.3 Perl: 5.16.3 and 5.26.3 CentOS: 7.4

[inopar]

I was in the same situation. However, it was improved by changing the version of perl5db.pl. If its helpful then im happy.

■ NG
CentOS: 7.3.1611
VS Code: 1.38.1
PadWalker: 2.3
Perl: 5.16.3
perl5db.pl: 1.37

■ OK
CentOS: 7.3.1611
VS Code: 1.38.1
PadWalker: 2.3
Perl: 5.16.3
perl5db.pl: 1.44          ← Update

I tried two ways to use perl5db.pl version 1.44

• Method 1

1.  Run 「perldoc -l perl5db.pl」 command to find the path of perl5db.pl
2.  downloaded from 「https://fastapi.metacpan.org/source/SHAY/perl-5.20.1/lib/perl5db.pl」
3.  Replace perl5db.pl file

• Method 2

1 . downloaded from 「https://fastapi.metacpan.org/source/SHAY/perl-5.20.1/lib/perl5db.pl」
2.  Put it in your favorite directory.For example「/home/user/perl5db-1.44.pl」
3.  Specify perl5db.pl and execute the Perl debug command. 
　  ・Run Command
         「PERL5DB='BEGIN {require "/home/user/perl5db-1.44.pl"}' perl -d test.pl」
　  ・launch.json　
           "env" : {
              "PERL5DB" : "BEGIN {require '/home/user/perl5db-1.44.pl'}"
           }

[raix]

@inopar I remember experiencing inconsistencies in perldb - I did consider if the extension could check / install perldb and padwalker at fixed versions (to rule out a couple of dependencies)

[guobbs]

@raix @inopar I have a same problem on centos7.7 today, then I update the perl version from perl5.16 to perl 5.22 and reinstall PadWalker module, thers is no problem now!

[ganezdragon]

@raix @GUOBBS any other alternatives than updating from perl5.16 ?

[guobbs]

@raix @GUOBBS any other alternatives than updating from perl5.16 ? yon can find @inopar 's answer，try it, its maybe help you.

[raix]

@GUOBBS @ganezdragon @inopar just to be sure is the solution to upgrade perl5db.pl to 1.44? (I did have an experiment branch 1-2 years back actually adding a specific version of perl5db.pl)

[victorkolbin]

@raix changing perl5db.pl's version to 1.44 did not work for me CentOS: 7.4.1708 PadWalker: 1.96 VS Code: 1.25.1 Perl: 5.16.3 perl5db: changed from 1.37 to 1.44

[inopar]

@victorkolbin Try updating PadWalker version from 1.96 to 2.3