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

Debugging gets stuck with visualParseTree set to true #37

Closed
Shodan79 opened this issue Jun 12, 2018 · 6 comments
Closed

Debugging gets stuck with visualParseTree set to true #37

Shodan79 opened this issue Jun 12, 2018 · 6 comments

Comments

@Shodan79
Copy link

@Shodan79 Shodan79 commented Jun 12, 2018

Hi,

up front let me say thank you very much for this fantastic extension!

I have configured the launch task according to documentation, and it prints correctly to the debug console, visual Parse Tree does not work though:

    "version": "2.0.0",
    "configurations": [        
        {
            "name": "antlr4-flow",
            "type": "antlr-debug",
            "request": "launch",
            //"input": "${workspaceFolder}/${command:AskForTestInput}",
            "input": "test.flow",
            "grammar": "flow.g4",
            "startRule": "file",
            "printParseTree": true,
            "visualParseTree": true
        }
    ]

If I set "visualParseTree" to false the debugger will start, print results to debug console and exit.

If it is set to true the debugger will start, print results to the debug console and then apparently get stuck (the toolbar with pause, restart, stop buttons is displayed but no visual parse tree appears).

Best regards,
Robert.

@mike-lischke

This comment has been minimized.

Copy link
Owner

@mike-lischke mike-lischke commented Jun 12, 2018

Can you attach your grammar here, so I can take a look what might be wrong?

@Shodan79

This comment has been minimized.

Copy link
Author

@Shodan79 Shodan79 commented Jun 13, 2018

This is the grammar file I am playing with:
https://drive.google.com/open?id=1cmxPnnGVKlV1LouLHjIIUgWn3zKbz5dz

I found this in "renderer1.log", perhaps it is helpful:

[2018-06-13 08:56:15.990] [renderer1] [info] no standard startup: panel is active
[2018-06-13 08:57:06.983] [renderer1] [error] [UriError]: If a URI contains an authority component, then the path component must either be empty or begin with a slash ("/") character: Error: [UriError]: If a URI contains an authority component, then the path component must either be empty or begin with a slash ("/") character
at c:\Program Files\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:45:689
at t.e (c:\Program Files\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:45:1003)
at new t (c:\Program Files\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:47:756)
at t.e.with (c:\Program Files\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:46:715)
at Object.getTextProviderUri (C:\Users\Robert.vscode\extensions\mike-lischke.vscode-antlr4-2.0.3\out\src\frontend\TextContentProvider.js:85:20)
at GrapsDebugger.debugger.on (C:\Users\Robert.vscode\extensions\mike-lischke.vscode-antlr4-2.0.3\out\src\frontend\AntlrDebugAdapter.js:264:94)
at emitNone (events.js:86:13)
at GrapsDebugger.emit (events.js:188:7)
at Immediate._ (C:\Users\Robert.vscode\extensions\mike-lischke.vscode-antlr4-2.0.3\out\src\backend\GrapsDebugger.js:261:18)
at runCallback (timers.js:672:20)
at tryOnImmediate (timers.js:645:5)
at processImmediate [as _immediateCallback] (timers.js:617:5)

@KarimLUCCIN

This comment has been minimized.

Copy link

@KarimLUCCIN KarimLUCCIN commented Jun 14, 2018

I think I also have that issue. It was working fine in VS Code 1.23.1 but doesn't work on 1.24.1 (the same grammar)

@fdammacco

This comment has been minimized.

Copy link

@fdammacco fdammacco commented Jun 19, 2018

Same issue here, VS Code version 1.24.1

@TheGenezis

This comment has been minimized.

Copy link

@TheGenezis TheGenezis commented Jul 9, 2018

Any updates please? @mike-lischke

mike-lischke added a commit that referenced this issue Jul 13, 2018
Also the backend tests from the former antlr4-graps module should now run automatically.
@KarimLUCCIN

This comment has been minimized.

Copy link

@KarimLUCCIN KarimLUCCIN commented Jul 15, 2018

It works now, thanks for fixing it @mike-lischke ! :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
5 participants
You can’t perform that action at this time.