-
Notifications
You must be signed in to change notification settings - Fork 13.4k
RUST_LOG=::rt::backtrace appears to do nothing #6823
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Comments
per IRC conversation, this is apparently known to be broken (on Mac OS X). Not much help, I know... gdb does apparently work, though, if that helps. |
Nominating for production-ready. |
closing as dup of 1650 |
flip1995
pushed a commit
to flip1995/rust
that referenced
this issue
Mar 11, 2021
Use diagnostic or language items instead of paths I think that gets everything except ones used in a list of paths to check. changelog: none
flip1995
pushed a commit
to flip1995/rust
that referenced
this issue
Mar 11, 2021
Don't assume lang items will exist. ~~Should fix lintcheck warnings caused by rust-lang#6823~~ See below changelog: None
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
When running a program that hits an
assert!()
, usingRUST_LOG=::rt::backtrace
makes no difference in the output. No backtrace is reported on the task failure.This is with
rustc 0.6 (c8c60f0 2013-05-28 18:34:51 -0700)
running on Mac OS X 10.8.3The text was updated successfully, but these errors were encountered: