Skip to content
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

No response for 'evaluate' request when program is running #14843

Closed
isidorn opened this issue Nov 2, 2016 · 1 comment
Closed

No response for 'evaluate' request when program is running #14843

isidorn opened this issue Nov 2, 2016 · 1 comment
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug debug Debug viewlet, configurations, breakpoints, adapter issues upstream Issue identified as 'upstream' component related (exists outside of VS Code) verified Verification succeeded

Comments

@isidorn
Copy link
Contributor

isidorn commented Nov 2, 2016

Steps to Reproduce:

var t = 5;
debugger;
  1. Once you hit the breakpoint add t to a watch expression -> it is nicely evaluated
  2. Continue the program -> notice how t does not update to not available. This is due to the fact that evalute request is not sending a response
  3. I would expect the evalute to always give a response no matter the state of the program
@isidorn isidorn added bug Issue identified by VS Code Team member as probable bug debug Debug viewlet, configurations, breakpoints, adapter issues labels Nov 2, 2016
@weinand
Copy link
Contributor

weinand commented Feb 14, 2017

@isidorn with "hit breakpoint" you mean "stopping on the debugger statement", right?

If I press continue, the program comes to an end (but does not correctly terminate because of this long standing node issue) and the watch expression runs into a timeout after 10 seconds (which is the correct behaviour).

If I modify the program by adding some "waiting code" at the end, the "continue" triggers the watch expression which results in an expected "not available" error.

@weinand weinand closed this as completed Feb 14, 2017
@weinand weinand added the upstream Issue identified as 'upstream' component related (exists outside of VS Code) label Feb 14, 2017
@isidorn isidorn added the verified Verification succeeded label Feb 22, 2017
@vscodebot vscodebot bot locked and limited conversation to collaborators Nov 18, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue identified by VS Code Team member as probable bug debug Debug viewlet, configurations, breakpoints, adapter issues upstream Issue identified as 'upstream' component related (exists outside of VS Code) verified Verification succeeded
Projects
None yet
Development

No branches or pull requests

2 participants