Skip to content

log to stderr instead of stdout #1750

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

Closed
wants to merge 1 commit into from
Closed

Conversation

tedhorst
Copy link
Contributor

@tedhorst tedhorst commented Feb 4, 2012

includes rustc diagnostics
runtest updated to check stderr for errors

includes rustc diagnostics
runtest updated to check stderr for errors
@graydon
Copy link
Contributor

graydon commented Feb 4, 2012

Think I'm fine with this. Anyone else object?

@brson
Copy link
Contributor

brson commented Feb 4, 2012

Merged.

@brson brson closed this Feb 4, 2012
@brson
Copy link
Contributor

brson commented Feb 7, 2012

Unfortunately this caused a mysterious issue on windows: #1769, so I've reverted it for now.

@brson
Copy link
Contributor

brson commented Feb 7, 2012

And for some reason I can't reopen this pull request.

@brson
Copy link
Contributor

brson commented Feb 7, 2012

I opened #1770 for logging to stderr since I couldn't reopen this one.

@tedhorst
Copy link
Contributor Author

tedhorst commented Feb 7, 2012

I removed the flush because I thought stderr was supposed to be unbuffered. Is that not true on windows?

You probably can't reopen because I deleted the branch after the merge.

@brson
Copy link
Contributor

brson commented Feb 7, 2012

I do not know. I did try flushing stderr but it didn't help.

@tedhorst tedhorst mentioned this pull request Feb 9, 2012
celinval added a commit to celinval/rust-dev that referenced this pull request Jun 4, 2024
* Enable option to dump MIR after reachability analysis

For now, we just tag along the `--emit mir` option that can be provided
to rustc. We use the extension `.kani.mir` to avoid conflict with the
one generated from rustc.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants