-
Notifications
You must be signed in to change notification settings - Fork 12.7k
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
Panic when setting RUST_MIN_STACK incorrectly #126431
Comments
#125302 looks like the PR I would nominate for backporting. Not sure if this rises to the level of doing a point release if this is the only problem, given that it requires a bad env var value. |
I am nominating #125302 for a stable backport. I recommend actually carrying out such a backport only if there are other reasons to do a stable release, at which point it may make sense for it to a catch a ride. |
@jeffreyssmith2nd fwiw, if this was happening before, my understanding is that it was not erroring, but rather simply being ignored, so you can probably unset it. |
@jeffreyssmith2nd can you report back if #125302 fix the issue for you? Should be available in a nightly (maybe also already in beta) . Thanks |
Looks good to me, available on both nightly and beta 👍 |
This has been fixed in nightly, but was an unexpected panic to encounter on stable. The weird number format is thanks to CircleCI/YAML mangling, I would probably expect this to fail but with at least the error message as seen in nightly.
Code
cargo new bad-env cd bad-env RUST_MIN_STACK=1e+07 cargo +stable build
Meta
rustc --version --verbose
:Error output
Backtrace
The text was updated successfully, but these errors were encountered: