-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unverified Breakpoints with "Python" or "Integrated Teminal/Console" #87
Comments
From @mike-pt on March 6, 2017 15:53 I wonder if this is similar too --> microsoft/vscode-go#689 ? The problem seems like the same, and maybe this can hint on a solution... |
From @mike-pt on May 10, 2017 14:32 This still happens in the most recent stable version on vscode and pythonVSCode, however its a bit different. I'm able to "stop at the breakpoint" but its still marked unverified? :| |
From @mike-pt on July 6, 2017 23:15 any update on this? |
Yes I still see it but it stops at the breakpoint as I mentioned in the last comment, I'm unsure if this is related to the fact that I'm calling args... in simpler scripts with just a "runsomefile.py" and no args... or when using "${file}" it doesn't do it... Also in the "running script" the breakpoints show "RED" and are not "unverified" |
|
Unfortunately this is code under NDA and I can't share any portion of it. I might be able to use something else though... and see if it also happens, but so far in 2 projects where we have lots of classes/function and import from those this happens... If I'm simply running a "sample.py" all the breakpoints work (come to think of it even with args... so that's not it) Maybe the issue is more generic happens if the file is not the main script? I'll do some more tests to check though |
Ok that seems to be the case files that are not the "running program" (i.e modules) get this unverified breakpoint issue... I.E. using a simple moduletest.py (that I import on a main py file) I am literally copy pasting from: |
Also I forgot to add I original reported this for Win 10 but this was just tested on OSX (Its still happening on Windows though) |
Thanks |
I simply copy pasted the code from the link above, to Do you need me to upload that go gist? or something? I'm using "cmd + shift+ D" on the mac with the test.py file opened while doing this As for the launch.json here it goes: And settings.json |
Able to replicate when debugging Python unit tests. |
From @mike-pt on March 5, 2017 16:2
Environment data
VS Code version: 1.10.1
Python Extension version: 0.5.9
Python Version: 2.7
OS and version: Windows 10
Actual behavior
Trying to set break points on inner modules set then as
Unverified Breakpoint
and debugger skips those, setting than on theprogram
file seems to work.Expected behavior
It should be possible to create breakpoints anywhere in the code, even if its not the "program" file
Not sure if its related to my custom launch config, but I'm simply specifying args and the program to run
My launch.json (if dealing with debugger issues):
The same thing happens if I use args/program in a similar way on "python" (without Terminal/Console).
Keeping program as "${file}" also ends in the same behavior.
Copied from original issue: DonJayamanne/pythonVSCode#791
The text was updated successfully, but these errors were encountered: