You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 13, 2021. It is now read-only.
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?
The text was updated successfully, but these errors were encountered:
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?
The text was updated successfully, but these errors were encountered: