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

Step over not working in attached node (electron) #7051

Closed
dbaeumer opened this issue May 31, 2016 · 2 comments
Closed

Step over not working in attached node (electron) #7051

dbaeumer opened this issue May 31, 2016 · 2 comments
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug debug Debug viewlet, configurations, breakpoints, adapter issues *not-reproducible Issue cannot be reproduced by VS Code Team member as described

Comments

@dbaeumer
Copy link
Member

  • VSCode Version: alpha
  • OS Version: Windows 10

Steps to Reproduce:

  1. clone vscode-elint, cd eslint && npm install && cs ../eslint-server && npm install
  2. open code on eslint and eslint-server folder. In both instances start build (Ctrl+Shift+B)
  3. in eslint press F5
  4. open a workspace that has JS files and eslint installed
  5. go to vscode that has eslint-server open
  6. attach
  7. open server.ts
  8. set a breakpoint at line 175
  9. go to the launched VS Code instance
  10. type into the js file. Observe: breakpoint is hit
  11. click step over

Observe: debugger continues

@dbaeumer dbaeumer added the debug Debug viewlet, configurations, breakpoints, adapter issues label May 31, 2016
@weinand weinand changed the title Step ovre not working in attached node (electron) Step over not working in attached node (electron) Jun 3, 2016
@weinand
Copy link
Contributor

weinand commented Jun 8, 2016

@dbaeumer most likely you are running into this node bug: nodejs/node#7219

@weinand weinand added the bug Issue identified by VS Code Team member as probable bug label Jun 8, 2016
@weinand weinand added the *not-reproducible Issue cannot be reproduced by VS Code Team member as described label Nov 20, 2017
@vscodebot
Copy link

vscodebot bot commented Nov 20, 2017

This issue has been closed because the problem could not be reproduced either because it is already fixed in later versions of the product or because it requires additional details on how to reproduce it. See also our issue reporting guidelines.

Happy Coding!

@vscodebot vscodebot bot closed this as completed Nov 20, 2017
@vscodebot vscodebot bot locked and limited conversation to collaborators Jan 5, 2018
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 *not-reproducible Issue cannot be reproduced by VS Code Team member as described
Projects
None yet
Development

No branches or pull requests

2 participants