Hi @richterger, dear Gerald,
many thanks for your great work!
Currently I'm running VSCode with Win11 and Perl in WSL und a proper und current installation of your VSCode extension and your LanguageServer.
In my very simply example I'm setting a first breakpoint in start.pl wich works and stops the debugger as expected.
Then I would like to set a second breakpoint within the function "something" in the module "test.pm" wich is located in the subdirectory "Modules" in the workspace.
When I start debugging the first breakpoint works as expected and the debugger stops.
The second breakpoint-Dot in VSCode is getting gray und the debugger didn't stop.
Here is my example:
Workspace: ~/projects/test/
containing file start.pl
and the subdirectory Modules/
containing test.pm
content of ~/projects/test/start.pl
#!/usr/bin/perl
package main;
use strict;
use warnings;
use lib '.';
# include file test.pm in subdirectoty "Modules"
use Modules::test;
# first working breakpoint in the following line
print "something\n";
# call function "something" in Modules/test.pm
Modules::test->something();
content of ~/projects/test/Modules/test.pm
package Modules::test;
use strict;
use warnings;
sub something
{
# I want to set the Breakpoint in the following line
print "something\n";
}
return 1;
But - after stopping at the first breakpoint in start.pl:
If I step-in (F11) from start.pl into the funtion-call "something", then VSCode opens "Modules/test.pm" in a new readonly page where I'm able to set my desired breakpoint (while debugging) - wich will work.
Noticeable is that the shown path when hovering with the mouse over the pages tab is "Modules/test.pm".
When opening the file by double-clicking from within the workspace-Window of VSCode the full path as mouse-over-info is "~/procests/test/Modules/test.pm".
Here is the logging of successfully setting the breakpoint in test.pm:
Hi @richterger, dear Gerald, many thanks for your great work!
Currently I'm running VSCode with Win11 and Perl in WSL und a proper und current installation of your VSCode extension and your LanguageServer.
In my very simply example I'm setting a first breakpoint in start.pl wich works and stops the debugger as expected. Then I would like to set a second breakpoint within the function "something" in the module "test.pm" wich is located in the subdirectory "Modules" in the workspace.
When I start debugging the first breakpoint works as expected and the debugger stops. The second breakpoint-Dot in VSCode is getting gray und the debugger didn't stop.
Here is my example:
Workspace: ~/projects/test/ containing file start.pl and the subdirectory Modules/ containing test.pm
content of ~/projects/test/start.pl
content of ~/projects/test/Modules/test.pm
content of ~/projects/test/.vscode/settings.json
content of ~/projects/test/.vscode/launch.json
Here is some logging from the Perl Language Server:
The first working breakpoint in start.pl
The second non-working breakpoint in Modules/test.pm
But - after stopping at the first breakpoint in start.pl: If I step-in (F11) from start.pl into the funtion-call "something", then VSCode opens "Modules/test.pm" in a new readonly page where I'm able to set my desired breakpoint (while debugging) - wich will work.
Noticeable is that the shown path when hovering with the mouse over the pages tab is "Modules/test.pm". When opening the file by double-clicking from within the workspace-Window of VSCode the full path as mouse-over-info is "~/procests/test/Modules/test.pm".
Here is the logging of successfully setting the breakpoint in test.pm:
Bug or feature - or my fault!? ;)