-
Notifications
You must be signed in to change notification settings - Fork 346
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
MIRI_LOG no longer works #2778
Comments
Line 199 in 1bc3e00
|
Ah, so that's the diff. Yeah Miri deliberately delayed calling logger initialization until pretty late, to avoid getting log spam from the rustc part of interpretation (in particular from const-eval during MIR building). This used to work because rustc_driver didn't force-init the loggers. Now it does, so this hack stopped working... Sadly we also cannot change log filters at runtime, so looks like avoiding the const-eval log spam when debugging Miri has become impossible? :( |
Ah yes, we even discussed a similar situation in the PR itself. I'll change it so that we stop logging so early |
Maybe you could implement a new |
Replace a command line flag with an env var to allow tools to initialize the tracing loggers at their own discretion fixes rust-lang/miri#2778 this was introduced in rust-lang#104645, so this PR reverts the flag-part and uses an env var instead.
Replace a command line flag with an env var to allow tools to initialize the tracing loggers at their own discretion fixes rust-lang/miri#2778 this was introduced in rust-lang#104645, so this PR reverts the flag-part and uses an env var instead.
Replace a command line flag with an env var to allow tools to initialize the tracing loggers at their own discretion fixes rust-lang#2778 this was introduced in rust-lang/rust#104645, so this PR reverts the flag-part and uses an env var instead.
Something semi-recently seems to have broken MIRI_LOG:
My guess would be that the loggers are initialized twice, but it's not very clear -- we are just getting a generic
SetGlobalDefaultError
.@oli-obk any idea what might have caused this change in behavior?
The text was updated successfully, but these errors were encountered: