search

raix / vscode-perl-debug

LOOKING FOR MAINTAINERS. Perl debugger extension for visual studio code
MIT License
63 stars 35 forks source link

Debugger not moving to next line #43

Open tarakeshp opened 6 years ago

tarakeshp commented 6 years ago

I am using Mojolicious Framework. When the server is started the debugger starts and do not respond/proceed to "Next Step" and hangs on there. Any Idea ? image image

raix commented 5 years ago

it seems like an issue in the path transformation, what OS and perl version/distribution?

oneForCode commented 5 years ago

Thanks for an awesome extension! I have the same issue. I connect to remote machine via SSH and use port forwarding to debug, but file system structures are different at the target machine and the one that has the VS Code on it.

Therefore, all my breakpoints in VSCode appear in grey and if you hover over them they say "Unverified breakpoint", and hitting "Step Over (F10)", or any other button does not move the current execution line forward.

I verified that commands typed into VS Code Debug Console are transmitted and executed correctly to the remote perl installation (so I can type 'n' and press enter and advance the remote script to the next line, but nothing moves in the IDE).

Can you help please? Thanks!

PS. I use MacOS for VS Code, and Linux for the remote box. Perl v5.10.1 (*) built for x86_64-linux-thread-multi Thx!

PS.2 Just for a test I created the same folder structure on my VS Code machine to match the folders on the remote machine (so the same absolute path is in both), and yet the same problem persists.

Any ideas? Thank you very much!

dseynhae commented 4 years ago

I am not sure if the title reflects the problem illustrated.

However, I seem to have the same problem, debugging a set of local Perl files: My breakpoints turn grey ("unverified break points").

Before starting the debugging, the 'Run' View shows the breakpoints in red; Clicking on them immediately jumps to the corresponding line in the source code. And when I hit F5 (Start Debugging), the breakpoints behave normal as well. However, during the debugging, they turn grey; I have no idea what triggers this, however it seems that adding/removing a break point during the debugging might be a way to reproduce this...

Working on Linux:

Version: 1.44.2
Commit: ff915844119ce9485abfe8aa9076ec76b5300ddd
Date: 2020-04-16T17:50:03.709Z
Electron: 7.1.11
Chrome: 78.0.3904.130
Node.js: 12.8.1
V8: 7.8.279.23-electron.0
OS: Linux x64 3.10.0-957.21.3.el7.x86_64

I don't recall seeing this behavior on Linux (with the same Perl files).

For me to debug this in a bit more reasonable way, does anybody know where VS Code (or the Perl Debug extension) stores the breakpoints in LInux???

raix commented 4 years ago

(There is an issue if path//file name contains certain chars)