-
Notifications
You must be signed in to change notification settings - Fork 34
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
Removing breakpoint from VSCode doesn't work #17
Comments
I can't duplicate. Can you provide a minimal VSCode folder that shows this? |
@BugraBarin I added a Zip file with complete extension project and fleshed out repro steps. |
Thanks that did it. Breakpoint doesn't have to be in a loop either. I am also seeing an assertion within VSCode when trying to remove the breakpoint and the message never gets sent to our debugger. This definitely looks to be all occurring within the VSCode extension. |
So then we should probably prepare an example for standalone Ruby and submit that to the VSCode extension? (Any idea how one run a Ruby debug server for standalone Ruby?) |
That would be worth pursuing. Something about that folder may be causing it, maybe the path names. |
Why would the path names be of significance? I'm able to set/remove breakpoint as long as the debugger isn't busy stepping through code. |
I managed to reproduce it with standalone Ruby. Even found an existing issue: Though it's nearly two years old... :/ |
Good find! We may have to dig into it ourselves. |
Any experience with VSCode extension development? |
When I set a breakpoint in VSCode, then try to remove it during a debug session it continues to break.
In this current scenario where I observe that I set a breakpoint within a loop. After hitting the breakpoint I then remove it and continue execution. But the code continues to break at the line where the breakpoint used to be. VSCode no longer lists any breakpoints.
Seems to be a synchronization issue.
vs-code-debug-issue-17.zip
Expected behaviour is that the loop continues without hitting the removed breakpoint.
Observed behaviour is that the breakpoint continues to break.
Compare this to RubyMine which works as expected:
The text was updated successfully, but these errors were encountered: