-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Problem with debugger #4238
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
Comments
@boazdori, thanks for letting us know about this problem and giving us plenty of information. Was this working under an earlier version of the extension? |
Yes it was
|
@boazdori, do you have |
maybe dupe of #4223? |
Because we have not heard back with the information we requested, we are closing this issue for now. If you are able to provide the info later on then we will be happy to re-open this issue to pick up where we left off. |
Uh oh!
There was an error while loading. Please reload this page.
Environment data
Version: 1.30.2 (user setup)
Commit: 61122f88f0bf01e2ac16bdb9e1bc4571755f5bd8
Date: 2019-01-07T22:54:13.295Z
Electron: 2.0.12
Chrome: 61.0.3163.100
Node.js: 8.9.3
V8: 6.1.534.41
OS: Windows_NT x64 10.0.17134
Extension version (available under the Extensions sidebar): 2019.1.0
Expected behavior
brake set to given line
debugger is chosen
running in debug mode
The process stops at the brake line
Actual behavior
after running the debugger the process doesn't reach the breakpoint
Logs
Output for
Python
in theOutput
panel (View
→Output
, change the drop-down the upper-right of theOutput
panel toPython
)Output from
Console
under theDeveloper Tools
panel (toggle Developer Tools on underHelp
; turn on source maps to make any tracebacks be useful by runningEnable source map support for extension debugging
)picture of the screen i see
https://user-images.githubusercontent.com/26312908/52057505-db27ea80-256d-11e9-81cd-44127a4d8b85.png
The text was updated successfully, but these errors were encountered: