Closed brikken closed 4 years ago
I am facing the same issue in Ubuntu Linux. Breakpoints are being ignored. vscode version: 1.33.1 Linux Kernel: x64 4.15.0-47-generic
Same problem to me Any solution here?
There was a problem with breakpoint resolution, which I fixed recently. Can you guys try the latest version from the vscode marketplace and let me know if that solves your issues?
I still had the test from my original post lying around, so I tried it again. Now it breaks at the breakpoint, but both stepping over (F10) and stepping in (F11) finishes the debugging session and outputs the parse tree to the debug log. If that's a real issue, I'll create a new one.
hi @mike-lischke, which version this issue was fixed at? I am still seeing this issue in version v2.2.4.
vscode version is: Version: 1.64.0 (user setup) Commit: 5554b12acf27056905806867f251c859323ff7e9 Date: 2022-02-03T04:22:20.678Z Electron: 13.5.2 Chromium: 91.0.4472.164 Node.js: 14.16.0 V8: 9.1.269.39-electron.0 OS: Windows_NT x64 10.0.19043
@elipersonal Please don't hijack an already closed bug. Usually such bugs (particularly when they are so old) have completely different circumstances to consider, than your current problem. Instead, open a new bug. Thanks.
I am sorry, i am fairly new to this. will open a new bug instead. thanks again
I've set a breakpoint in my grammar, but debugging (F5) doesn't stop execution at the breakpoint. It simply continues right to the end and produces the parse tree.
Grammar
launch.json
In addition, I have to specify the "grammar" and "startRule" elements for debugging to even work, even though the grammar file is active in the editor.
input.txt
Folder with grammar
VS Code
Latest version of the extension (just installed)