Open glyph opened 2 weeks ago
Does that not happen with other parsers?
Does that not happen with other parsers?
Only tried python-ts-mode
, but no, not with that one.
Can you get a stack trace or core dump?
There's an ips
file that macOS captured, which appears to contain a stack trace, but the only tree-sitter thing I see on the stack seems to be Ftreesit_node_type
. If this is helpful, though, here it is:
What I can tell from this is that it's trying to access a NULL pointer somewhere.
I can't reproduce the crash on Arch Linux. It might be a macOS or ARM-specific issue. I suggest trying a few more parsers and submitting a bug report to emacs if any of them also crash.
I've now tried python, javascript, java, and rust, and none have issues
(Or, none have this specific issue).
Is there any diagnostic I can perform locally that will produce a more useful artifact for you?
Maybe @amaanq can help with that.
Did you check existing issues?
Tree-Sitter CLI Version, if relevant (output of
tree-sitter --version
)tree-sitter 0.22.6
Describe the bug
Steps To Reproduce/Bad Parse Tree
emacs -nw a.toml
see the segfautl
Expected Behavior/Parse Tree
I expect it to not segfault
Repro
See above