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

Restarting a broken in pwa-node attach doesn't work #270

Closed
alexr00 opened this issue Jan 28, 2020 · 3 comments
Closed

Restarting a broken in pwa-node attach doesn't work #270

alexr00 opened this issue Jan 28, 2020 · 3 comments
Assignees
Milestone

Comments

@alexr00
Copy link
Member

alexr00 commented Jan 28, 2020

Testing microsoft/vscode#89393 on Windows

  • Run the existing, not pwa, Launch VS Code launch config in the vscode project.
  • Modify the Attach to Extension Host config to be pwa-node and run it
  • It attaches nicely and you can debug. Set a break point and hit the break point in the extension host.
  • Hit the Restart button in the debug toolbar
    Expected: The extension host will be re-attached to and I'll be at my same hit breakpoint.
    Actual: I'm not sure what happens. I think that it never re-attaches, and I don't see that execution is still paused on my breakpoint.
@alexr00 alexr00 transferred this issue from microsoft/vscode Jan 28, 2020
@connor4312 connor4312 added this to the February 2020 milestone Feb 3, 2020
@connor4312 connor4312 added feature-request Request for new features or functionality bug Issue identified by VS Code Team member as probable bug labels Feb 3, 2020
@connor4312
Copy link
Member

connor4312 commented Feb 4, 2020

Expected: The extension host will be re-attached to and I'll be at my same hit breakpoint.
Actual: I'm not sure what happens. I think that it never re-attaches, and I don't see that execution is still paused on my breakpoint.

For me the debugger disconnects and reattaches when hitting the "restart" button.

When the debugger detaches, Node/V8 will automatically continue execution, so when reattaching it won't be at the same breakpoint. I see the same behavior with the existing debugger, which I tested by seeing the counter increment in

let counter = 0;
setInterval(() => {
  console.log(counter++); // <- breakpoint here
}, 1000);

@connor4312 connor4312 added the info-needed Issue requires more information from poster label Feb 4, 2020
@alexr00
Copy link
Member Author

alexr00 commented Feb 4, 2020

In that case, this isn't an issue. I must have just triggered the same breakpoint twice when trying the same scenario with the old debugger.

@alexr00 alexr00 closed this as completed Feb 4, 2020
@connor4312
Copy link
Member

Okay, thanks for the confirmation! 🙂

@connor4312 connor4312 removed info-needed Issue requires more information from poster bug Issue identified by VS Code Team member as probable bug feature-request Request for new features or functionality labels Feb 4, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants