[scip] "thread 'main' has overflowed its stack" since nightly-2025-01-21

[glandium]

Steps to reproduce:

• Clone https://hg.mozilla.org/mozilla-central (mercurial) or https://github.com/mozilla/gecko-dev (git)
• Presumably, this would be reproductible with what you get out of the clone, but just in case, checkout 4d679baa3086ad410eb22618e50aea045424c0de (mercurial) or 3ee2e63c1b9cff116ff7bec1189e99fab6e1c15c (git)
• Copy .cargo/config.toml.in to .cargo/config.toml.
• Run rust-analyzer scip .

This is a serious regression in nightly and it's important to fix it before the next release.

Bad: rust-analyzer 1.86.0-nightly (f3d1d47 2025-01-20)
Good: rust-analyzer 1.86.0-nightly (9a1d156 2025-01-19)
... but of course the commits shown there are not from rust-analyzer itself... and it's not a submodule.

I /think/ the good one is 7b368b9 and the bad one is 93a5846.

[glandium]

Bisected to 5530167 (#18925)
Cc: @Veykril

[lnicola]

I was doing the same bisection and ended up on the same commit.

Anyway, my suggestion is to use our binaries from GitHub Releases instead of those in rustup. They're updated more often, and make it easier to switch versions or mix and match toolchains and rust-analyzer.