-
Notifications
You must be signed in to change notification settings - Fork 243
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
Debugger stops at first breakpoint and wont move on in VSCode 1.78 #7388
Comments
Hi, thanks for logging the issue. We also discovered it internally and we are already looking at it and what we should do from our end. Note there is also an issue opened on the vscode side: microsoft/vscode#181485 |
Also have same issue. |
I have the same issue. |
I'm experiencing the same! |
Same here |
1 similar comment
Same here |
+1 |
3 similar comments
+1 |
+1 |
+1 |
Same issue |
1 similar comment
Same issue |
same issue |
Hey all, You can stop reporting +1 on this issue :) The root cause seems to have been identified and will be fixed in VSCode. See microsoft/vscode#181485 for details. Workaround for now is to use v1.77.3. Just remember to disable the auto-update of VSCode by adding this to your settings: |
in [microsoft/vscode#181485] Neoster is talking about 1.78.2, debugging remains broken with that version, for me. the only permutation that worked for me was installing v1.77.3 and getting the latest stable AL extension (currently v11.0.827766) I hate to think of all the people right now pulling their hair out and just giving up on BC entirely because of this. edit: I take that back, I'm still one of the hair puller outers. It worked ONE TIME, then went back to "debugger frozen, unusable after hitting first breakpoint" mode. Nothing changed since I ran it before and hit "stop debugging". AFAIK. so yeah, 2 months of this, i wonder how many thousands of people this unsolved riddle has been given to. closed VSCode again, started it again, debugger works again. now it has something to do with the breakpoints, the one i want causes it, if an "break on error" breaks then it continues to work, but if it hits my manual point and it breaks on it then it freezes. if i move my point, the point isn't hit when it should have been, breaks on the error, then freeze as long as i use these versions and don't use any breakpoints it stays working |
@fartwhif Closed issues are no longer tracked by Microsoft. Regarding your break point issue, please create a new issue. |
I scoured the open issues and didn't find it, but found this one, I didn't realize it was closed. It shouldn't be closed. Since it's wrongfully closed by the high priests of Microsoft and there are new recent replacements that aren't closed you can be reassured that spamming the issue probably won't help and probably will waste everyone's time with further moderation haze and bureaucratic flagellation. I wish you and the rest of the AL dev pioneers the best. |
Debugger stops at the first breakpoint, but does not allow further navigation within the code.
The debugger does not accept any commands to move on:
Should be able to debug further. In VSCode version 1.77.3 this was still possible, a downgrade fixes this behavior.
Debugger stops at breakpoint and wont move on
AL Language: 11.0.787898
Visual Studio Code: 1.78.
The text was updated successfully, but these errors were encountered: