Proc-macro panicked: proc-macro server exited with signal: 6

[pi314ever]

rust-analyzer version: (eg. output of "rust-analyzer: Show RA Version" command, accessible in VSCode via Ctrl/⌘+Shift+P) 2024-08-27, installed through Mason

rustc version: (eg. output of rustc -V) 1.75.0

editor or extension: (eg. VSCode, Vim, Emacs, etc. For VSCode users, specify your extension version; for users of other editors, provide the distribution if applicable) neovim v0.10.2

relevant settings: (eg. client settings, or environment variables like CARGO, RUSTC, RUSTUP_HOME or CARGO_HOME)

repository link (if public, optional): (eg. rust-analyzer) cargo.features = "all", checkOnSave.command = "clippy"

code snippet to reproduce:

#[derive(Debug)]
struct Test {}

I have been encountering this bug while working on a project within a Docker environment that manually installs Rust and rust-analyzer, and I have not been able to figure out why. Any tips on how to diagnose this issue would be greatly appreciated.

[Veykril]

That snippet there doesn't even involve the proc-macro server so this is likely something odd with your setup, can't tell you what though unfortunately

[lnicola]

Signal 6 is SIGABRT, so some kind of abort().

[pi314ever]

Sorry that was a bad example. I am seeing this a lot with functions with tracing:

struct Test {}
impl Test {
  #[instrument(skip(self))]
  fn a(&self, b: usize, c: usize) {
     // Some things
  }
}

This causes my setup to highlight all of the function under the proc-macro server error with exit code 6 or 11. All other diagnostics within that function are not shown.

[pi314ever]

@Veykril I have updated the example errors I am encountering. Can you please look at this again?

[pi314ever]

Seems like this is only happening for Mason installed rust-analyzer and not rustacean.nvim's version. This may be a bug on Mason's integration?

[yuyang-ok]

I still have this issue . Is this problem solved???

[yuyang-ok]

@pi314ever I think I am not using mason installed rust-analyzer. I think I am using rust-analyzer installed via rustup.

I am still have this issue.

[39george]

Same issue with no mason, in neovim, rustaceanvim and latest rust-analyzer