-
Notifications
You must be signed in to change notification settings - Fork 13.3k
Stack overflow with lots of slice indexing. #107219
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
On a debug build from master, this code hangs infinitely (nightly reproduces the crash). Interestingly if I set |
I don't think the crash originates in the parser since Judging from the backtrace, the issue seems to come from
which is the demangled and manually cleaned up form of
I suspect the root cause is a stack overflow after @rustbot label -A-parser backtrace
|
Not a parser issue then, alright :-) Ah… looking back at the labels… @rustbot label T-compiler. |
This is not only with indexing, for example https://stackoverflow.com/q/75031602/7884305. The problem is that while the from the HIR on the passes are guarded with |
Presumably in the parser? (Since
cargo doc
andcargo fmt
crash, too.)Edit: Playing around with this some more, I believe that the
cargo fmt
could possibly be independent/even earlier. Also, turning on syntax highlighting for this on GitHub is somewhat slow, too, so I’m removing the highlighting 😅Repro:
The output from
cargo check
is also quite lengthy, involving lots of repetitions of paths such as……/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/librustc_driver-7dc221ef4086baf7.so(_RNvXsm_NtCs7SPt0dKrlGV_12rustc_expand6expandNtB5_19InvocationCollectorNtNtCs46SRgbRgNcU_9rustc_ast9mut_visit10MutVisitor10visit_expr+0xba)[0x7f2f0a1ea32a]
and……/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/librustc_driver-7dc221ef4086baf7.so(+0x16bfeb4)[0x7f2f0a1e6eb4
.@rustbot label I-crash, A-parser. As mentioned above, the
A-parser
is only a guess; feel free to adjust if the reason is something else.The text was updated successfully, but these errors were encountered: