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

Reapply all breakpoints seems like a bug exposed to the user #3389

Closed
alexdima opened this issue Feb 24, 2016 · 4 comments
Closed

Reapply all breakpoints seems like a bug exposed to the user #3389

alexdima opened this issue Feb 24, 2016 · 4 comments
Assignees
Labels
debug Debug viewlet, configurations, breakpoints, adapter issues feature-request Request for new features or functionality *out-of-scope Posted issue is not in scope of VS Code
Milestone

Comments

@alexdima
Copy link
Member

Testing #2832

Reapply all breakpoints -- I haven't seen such an action in other debuggers. IMHO it is the debugger's job to apply my breakpoints, and exposing an action to reapply all breakpoints seems like a workaround for a bug inside the debugger.

@isidorn isidorn added this to the Backlog milestone Feb 24, 2016
@isidorn isidorn added the debug Debug viewlet, configurations, breakpoints, adapter issues label Feb 24, 2016
@isidorn
Copy link
Contributor

isidorn commented Feb 24, 2016

I agree with your reasoning however sometimes it the debugger adapter does not know when is a good time to reapply breakpoints. @weinand can provide more details.

Also the react people really want this feature, so we will for sure not remove it.
We can make it more hidden by removing it from the viewlet and keeping it as a global workbench action
@weinand opinions?

@weinand
Copy link
Contributor

weinand commented Feb 24, 2016

We could get rid of this in the UI if we would call it on every stopped event. This would slow down stepping.

@alexdima
Copy link
Member Author

If you compare breakpoints to watch expressions, I find it nice that there is no refresh button on the watch expressions (the debugger knows when it's a good time to re-evaluate them).

Maybe the debugger could keep a list of function breakpoints it could not apply and every chance it gets it tries to reapply the function breakpoints until they were applied successfully. Or perhaps report it to the UI on every pause that this function breakpoint is not active, is active, etc.

@weinand weinand added the feature-request Request for new features or functionality label Feb 24, 2016
@weinand weinand assigned weinand and unassigned isidorn Feb 24, 2016
@weinand weinand added the *out-of-scope Posted issue is not in scope of VS Code label Dec 8, 2017
@vscodebot
Copy link

vscodebot bot commented Dec 8, 2017

This issue is being closed to keep the number of issues in our inbox on a manageable level, we are closing issues that have been on the backlog for a long time but have not gained traction: We look at the number of votes the issue has received and the number of duplicate issues filed. If you disagree and feel that this issue is crucial: We are happy to listen and to reconsider.

If you wonder what we are up to, please see our roadmap and issue reporting guidelines.

Thanks for your understanding and happy coding!

@vscodebot vscodebot bot closed this as completed Dec 8, 2017
@vscodebot vscodebot bot locked and limited conversation to collaborators Jan 22, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
debug Debug viewlet, configurations, breakpoints, adapter issues feature-request Request for new features or functionality *out-of-scope Posted issue is not in scope of VS Code
Projects
None yet
Development

No branches or pull requests

3 participants