-
Notifications
You must be signed in to change notification settings - Fork 1.8k
proc macro server crashed #6755
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
Comments
[rust-analyzer macro-error] [E] proc macro server crashed +1 |
rust-analyzer macro-error] [E] Empty result |
Otherwise, excessive highlight warning |
@Piping Could you reproduce the error? I don't understand your comments. |
@Sympatron can you try with the nightly version? |
@lnicola Seems to be fixed on nightly (version 0.3.413). |
@Sympatron I am using vim and Coc.vim together with rust-analyzer. I can reproduce crash in my workspace with a different project. ( I used My Coc Setup {
"rust-analyzer.cargo.loadOutDirsFromCheck": true,
"rust-analyzer.procMacro.enable": true,
// comment "rust-analyzer.diagnostics.disabled": [ "macro-error", "unresolved-proc-macro" ],
"rust-analyzer.updates.channel": "nightly"
} |
I use nvim + Coc.vim and after update to rust-analyzer-mac with version: |
The original crash in this issue is fixed. We can track further ones with no error messages under #6880. |
seems I've hit similar problem again, (I've seen heap-use-after-free error in neovim lsp.log, but didn't save it, can not confirm if the heap-use-after-free error is triggered by rust-analyzer). I'm using neovim builtin lsp coredump
my default toolchain |
@comicfans that's related to #8925, #8928, #8929 and #9047 (comment) (not sure we need three issues for it, though). You can either:
We won't be able to merge any fix soon, unfortunately. |
Uh oh!
There was an error while loading. Please reload this page.
When loading
atsamd-rs
BSPs,rust-analyzer
crashes.I don't have the VSCode Rust extension installed.
Steps to reproduce:
git clone https://github.com/atsamd-rs/atsamd.git
code atsamd/boards/itsybitsy_m4
settings.json:
Stack trace:
The text was updated successfully, but these errors were encountered: