vscode-perl-debug icon indicating copy to clipboard operation
vscode-perl-debug copied to clipboard

"Unverified breakpoint" when setting breakpoints in different file

Open ishaan-mehta opened this issue 4 years ago • 1 comments

For some reason, whenever my colleagues and I try to set a breakpoint in a Perl module that is used by a Perl script that we are debugging, the breakpoint in that module becomes a hollow circle with a grey outline instead of the red filled-in circle that usually signifies working breakpoints. Hovering over the circle shows an "Unverified breakpoint" label. The debugger does not stop at these unverified breakpoints.

However, if we set a breakpoint in the Perl script before it jumps to the module, we can then set a breakpoint in the module, and it will stop at the module.

Is this something wrong with the extension or something we are all doing wrong?

ishaan-mehta avatar Jul 07 '20 23:07 ishaan-mehta

I have the same problem... I have it for both local and remote sessions.

I have started to work around the problem (those unverified breakpoints don't work), by placing

$DB::single=1;

in the code... not ideal (and not always possible, when working with corporate/write-protected libraries)... But I would love to see this fixed!!!

dseynhae avatar Aug 12 '20 21:08 dseynhae