You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have been using the 'ANTLR4 View' vscode extension for the past 1 month in my Ubuntu 22.04. When debugging the grammar I had been using the parse tree visualizer, it used to show me the parse tree while debugging.
But since the upgrade to version 2.4.5 and a follow-up reload I realised my parse tree stopped visualizing. But when I returned to the previous version it's been working fine. I am unsure if upgrading the dependency caused a bug or if I am missing something.
The text was updated successfully, but these errors were encountered:
This might be related to this VS Code issue. I see many of these "invalid debug adapter" messages in the VS Code dev console, when running vscode-antlr4 as normal extension. However, when debugging the extension then debugging in it works nicely.
I have the same problem. Windows 11, vscode 1.86.0, antlr-vscode plugin version 2.4.5.
If I try work just with vscode then I do not see anything on "Show ANTLR graph for rule":
ANTLR-BUG-242.v001.mp4
if I try start antlr-vscode in debug mode then I see anything:
ANTLR-BUG-242.v002.mp4
Also I have the same problem with "Show grammar call graph". It show nothing in ordinary vscode run and show "call graph" in debug mode. Also I update vscode to 1.86.1, disable all vscode plugins and restart vscode.
I have been using the 'ANTLR4 View' vscode extension for the past 1 month in my Ubuntu 22.04. When debugging the grammar I had been using the parse tree visualizer, it used to show me the parse tree while debugging.
But since the upgrade to version 2.4.5 and a follow-up reload I realised my parse tree stopped visualizing. But when I returned to the previous version it's been working fine. I am unsure if upgrading the dependency caused a bug or if I am missing something.
The text was updated successfully, but these errors were encountered: