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

Debugger stops at first breakpoint and wont move on in VSCode 1.78 #7388

Closed
cosmo-skol opened this issue May 4, 2023 · 17 comments
Closed

Debugger stops at first breakpoint and wont move on in VSCode 1.78 #7388

cosmo-skol opened this issue May 4, 2023 · 17 comments
Assignees
Labels
accepted debugger Issues related to the debugger ships-in-future-update The issue is fixed in our 'master' branch and will ship in the next PREVIEW release

Comments

@cosmo-skol
Copy link

  1. Describe the bug

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:

  • Step over next line (F10)
  • Go to next line (F11)
  • Go to next breakpoint (F5)
  1. To Reproduce
  • Update to VSCode version 1.78
  • Set breakpoint in AL code.
  • Start debugging to breakpoint.
  • Try to move the debugger to another line of code
  1. Expected behavior

Should be able to debug further. In VSCode version 1.77.3 this was still possible, a downgrade fixes this behavior.

  1. Actual behavior

Debugger stops at breakpoint and wont move on

  1. Versions:

AL Language: 11.0.787898
Visual Studio Code: 1.78.

@nndobrev
Copy link
Contributor

nndobrev commented May 4, 2023

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

@nndobrev nndobrev self-assigned this May 4, 2023
@nndobrev nndobrev added debugger Issues related to the debugger accepted labels May 4, 2023
@nzcraig
Copy link

nzcraig commented May 5, 2023

Also have same issue.
VS Code 1.78

@smorv
Copy link

smorv commented May 8, 2023

I have the same issue.
VS Code 1.78

@tmajvdlaan
Copy link

I'm experiencing the same!

@ekom21-TL
Copy link

Same here

1 similar comment
@stefaanMLB
Copy link

Same here

@christianbraeunlich
Copy link

+1

3 similar comments
@RodionLobuzov
Copy link

+1

@minaskats
Copy link

+1

@DanielGoehler
Copy link
Contributor

+1

@JellebBE
Copy link

JellebBE commented May 9, 2023

Same issue

1 similar comment
@JurgenVh
Copy link

JurgenVh commented May 9, 2023

Same issue

@GhOnBc
Copy link

GhOnBc commented May 9, 2023

same issue

@jwikman
Copy link

jwikman commented May 9, 2023

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: "update.mode": "manual"

@JesperSchulz JesperSchulz added the ships-in-future-update The issue is fixed in our 'master' branch and will ship in the next PREVIEW release label May 10, 2023
@fartwhif
Copy link

fartwhif commented Jul 17, 2023

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: "update.mode": "manual"

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

@NKarolak
Copy link

@fartwhif Closed issues are no longer tracked by Microsoft. Regarding your break point issue, please create a new issue.

@fartwhif
Copy link

fartwhif commented Jul 18, 2023

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
accepted debugger Issues related to the debugger ships-in-future-update The issue is fixed in our 'master' branch and will ship in the next PREVIEW release
Projects
None yet
Development

No branches or pull requests