-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Debugger does not work when another trace function is set #218
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
Sometimes i encounter this issue as well. When i set the breakpoint on the first line, it would not stop. |
I am using flask, flask have inbuild debugger so while running the flask app with debug mode in vscode , vscode debugger not working. But when I disabled flask debugger, the vscode debugger works as excepted. So the problem is when inbuild debugger is present, vscode debugger not working until we disable inbuild debugger. |
@Sathisz ah, so you already have already called |
I have a similar issue, debuger runs the code, but doesn't stops on breakpoint. I see the output in the output window, but no stops in code. attempt to send more than one response for command launch(node:6204) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 1): TypeError: Cannot read property 'SendExceptionInfo' of null |
Maybe this can also be helpful. The output from developer tools:
|
Closing this as it requires https://github.com/microsoft/ptvsd to support it; please request there if you still want this feature. |
From @Sathisz on November 9, 2017 10:6
Environment data
VS Code version: 1.18
Python Extension version: latest
Python Version: 3.4.3
OS and version: Linux Mint 18.1
Actual behavior
No action performed
Expected behavior
Stops at the break point when it hits
Steps to reproduce:
Logs
Output from
Python
output panelOutput from
Console window
(Help->Developer Tools menu)Copied from original issue: DonJayamanne/pythonVSCode#1377
The text was updated successfully, but these errors were encountered: