VSCode messed debugging, watches, variables, evaluation with python
I just noticed my VSCode debugger stopped working. I messed it up by accident or maybe the update changed something. Either way, I have no clue what to change to get it working.
What doesn't work is Variable list during debugging - it is always empty. Watches show as not available, calls tack only displays paused on breakpoint. Breakpoints work but stepping over lines is not available. Also, trying to evaluate a piece of code gives:
Traceback (most recent call last):
File "/home/█/.vscode/extensions/ms-python.python-2018.10.1/pythonFiles/experimental/ptvsd/ptvsd/wrapper.py", line 1339, in done
fut.result()
File "/home/█/.vscode/extensions/ms-python.python-2018.10.1/pythonFiles/experimental/ptvsd/ptvsd/futures.py", line 40, in result
reraise(self._exc_info)
File "/home/█/.vscode/extensions/ms-python.python-2018.10.1/pythonFiles/experimental/ptvsd/ptvsd/futures.py", line 149, in callback
x = next(it)
File "/home/█/.vscode/extensions/ms-python.python-2018.10.1/pythonFiles/experimental/ptvsd/ptvsd/wrapper.py", line 1957, in on_evaluate
vsc_fid = int(args['frameId'])
KeyError: 'frameId'
I suppose it is a matter of some basic config but I can't find a solution
python visual-studio-code vscode-debugger
asked Nov 23 '18 at 12:00
Sane_or_notSane_or_not
1016
add a comment |
I just noticed my VSCode debugger stopped working. I messed it up by accident or maybe the update changed something. Either way, I have no clue what to change to get it working.
What doesn't work is Variable list during debugging - it is always empty. Watches show as not available, calls tack only displays paused on breakpoint. Breakpoints work but stepping over lines is not available. Also, trying to evaluate a piece of code gives:
Traceback (most recent call last):
File "/home/█/.vscode/extensions/ms-python.python-2018.10.1/pythonFiles/experimental/ptvsd/ptvsd/wrapper.py", line 1339, in done
fut.result()
File "/home/█/.vscode/extensions/ms-python.python-2018.10.1/pythonFiles/experimental/ptvsd/ptvsd/futures.py", line 40, in result
reraise(self._exc_info)
File "/home/█/.vscode/extensions/ms-python.python-2018.10.1/pythonFiles/experimental/ptvsd/ptvsd/futures.py", line 149, in callback
x = next(it)
File "/home/█/.vscode/extensions/ms-python.python-2018.10.1/pythonFiles/experimental/ptvsd/ptvsd/wrapper.py", line 1957, in on_evaluate
vsc_fid = int(args['frameId'])
KeyError: 'frameId'
I suppose it is a matter of some basic config but I can't find a solution
python visual-studio-code vscode-debugger
asked Nov 23 '18 at 12:00
Sane_or_notSane_or_not
1016
Please file a bug at github.com/microsoft/ptvsd and include any code you can to help reproduce this.
– Brett Cannon
Nov 26 '18 at 22:03
@BrettCannon I identified 2 problems: 1. Linux Mint software manager distributes an erratic version of VSCode, changing back to .deb from VS-page helped with KeyError I mentioned. 2. Debugging doesnt work with conda environment (not debugging itself, but watches/variables/ignoring breakpoints). Using virtualenv or no env for debugging pieces of code is a workaround for me. I will reproduce the problem later.
– Sane_or_not
Nov 28 '18 at 11:48
add a comment |
I just noticed my VSCode debugger stopped working. I messed it up by accident or maybe the update changed something. Either way, I have no clue what to change to get it working.
What doesn't work is Variable list during debugging - it is always empty. Watches show as not available, calls tack only displays paused on breakpoint. Breakpoints work but stepping over lines is not available. Also, trying to evaluate a piece of code gives:
Traceback (most recent call last):
File "/home/█/.vscode/extensions/ms-python.python-2018.10.1/pythonFiles/experimental/ptvsd/ptvsd/wrapper.py", line 1339, in done
fut.result()
File "/home/█/.vscode/extensions/ms-python.python-2018.10.1/pythonFiles/experimental/ptvsd/ptvsd/futures.py", line 40, in result
reraise(self._exc_info)
File "/home/█/.vscode/extensions/ms-python.python-2018.10.1/pythonFiles/experimental/ptvsd/ptvsd/futures.py", line 149, in callback
x = next(it)
File "/home/█/.vscode/extensions/ms-python.python-2018.10.1/pythonFiles/experimental/ptvsd/ptvsd/wrapper.py", line 1957, in on_evaluate
vsc_fid = int(args['frameId'])
KeyError: 'frameId'
I suppose it is a matter of some basic config but I can't find a solution
python visual-studio-code vscode-debugger
asked Nov 23 '18 at 12:00
Sane_or_notSane_or_not
1016
I just noticed my VSCode debugger stopped working. I messed it up by accident or maybe the update changed something. Either way, I have no clue what to change to get it working.
What doesn't work is Variable list during debugging - it is always empty. Watches show as not available, calls tack only displays paused on breakpoint. Breakpoints work but stepping over lines is not available. Also, trying to evaluate a piece of code gives:
Traceback (most recent call last):
File "/home/█/.vscode/extensions/ms-python.python-2018.10.1/pythonFiles/experimental/ptvsd/ptvsd/wrapper.py", line 1339, in done
fut.result()
File "/home/█/.vscode/extensions/ms-python.python-2018.10.1/pythonFiles/experimental/ptvsd/ptvsd/futures.py", line 40, in result
reraise(self._exc_info)
File "/home/█/.vscode/extensions/ms-python.python-2018.10.1/pythonFiles/experimental/ptvsd/ptvsd/futures.py", line 149, in callback
x = next(it)
File "/home/█/.vscode/extensions/ms-python.python-2018.10.1/pythonFiles/experimental/ptvsd/ptvsd/wrapper.py", line 1957, in on_evaluate
vsc_fid = int(args['frameId'])
KeyError: 'frameId'
I suppose it is a matter of some basic config but I can't find a solution
python visual-studio-code vscode-debugger
python visual-studio-code vscode-debugger
asked Nov 23 '18 at 12:00
Sane_or_notSane_or_not
1016
asked Nov 23 '18 at 12:00
Sane_or_notSane_or_not
1016
asked Nov 23 '18 at 12:00
Sane_or_notSane_or_not
1016
asked Nov 23 '18 at 12:00
Sane_or_notSane_or_not
1016
asked Nov 23 '18 at 12:00
Sane_or_notSane_or_not
1016
1016
Please file a bug at github.com/microsoft/ptvsd and include any code you can to help reproduce this.
– Brett Cannon
Nov 26 '18 at 22:03
@BrettCannon I identified 2 problems: 1. Linux Mint software manager distributes an erratic version of VSCode, changing back to .deb from VS-page helped with KeyError I mentioned. 2. Debugging doesnt work with conda environment (not debugging itself, but watches/variables/ignoring breakpoints). Using virtualenv or no env for debugging pieces of code is a workaround for me. I will reproduce the problem later.
– Sane_or_not
Nov 28 '18 at 11:48
add a comment |
Please file a bug at github.com/microsoft/ptvsd and include any code you can to help reproduce this.
– Brett Cannon
Nov 26 '18 at 22:03
@BrettCannon I identified 2 problems: 1. Linux Mint software manager distributes an erratic version of VSCode, changing back to .deb from VS-page helped with KeyError I mentioned. 2. Debugging doesnt work with conda environment (not debugging itself, but watches/variables/ignoring breakpoints). Using virtualenv or no env for debugging pieces of code is a workaround for me. I will reproduce the problem later.
– Sane_or_not
Nov 28 '18 at 11:48
Please file a bug at github.com/microsoft/ptvsd and include any code you can to help reproduce this.
– Brett Cannon
Nov 26 '18 at 22:03
Please file a bug at github.com/microsoft/ptvsd and include any code you can to help reproduce this.
– Brett Cannon
Nov 26 '18 at 22:03
@BrettCannon I identified 2 problems: 1. Linux Mint software manager distributes an erratic version of VSCode, changing back to .deb from VS-page helped with KeyError I mentioned. 2. Debugging doesnt work with conda environment (not debugging itself, but watches/variables/ignoring breakpoints). Using virtualenv or no env for debugging pieces of code is a workaround for me. I will reproduce the problem later.
– Sane_or_not
Nov 28 '18 at 11:48
@BrettCannon I identified 2 problems: 1. Linux Mint software manager distributes an erratic version of VSCode, changing back to .deb from VS-page helped with KeyError I mentioned. 2. Debugging doesnt work with conda environment (not debugging itself, but watches/variables/ignoring breakpoints). Using virtualenv or no env for debugging pieces of code is a workaround for me. I will reproduce the problem later.
– Sane_or_not
Nov 28 '18 at 11:48
add a comment |
0
active
oldest
votes
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53446345%2fvscode-messed-debugging-watches-variables-evaluation-with-python%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53446345%2fvscode-messed-debugging-watches-variables-evaluation-with-python%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Please file a bug at github.com/microsoft/ptvsd and include any code you can to help reproduce this.
– Brett Cannon
Nov 26 '18 at 22:03
@BrettCannon I identified 2 problems: 1. Linux Mint software manager distributes an erratic version of VSCode, changing back to .deb from VS-page helped with KeyError I mentioned. 2. Debugging doesnt work with conda environment (not debugging itself, but watches/variables/ignoring breakpoints). Using virtualenv or no env for debugging pieces of code is a workaround for me. I will reproduce the problem later.
– Sane_or_not
Nov 28 '18 at 11:48