Skip to content

rustc: make stack traces print for .span_bug/.bug. #12874

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

Merged
merged 1 commit into from
Mar 14, 2014

Conversation

huonw
Copy link
Member

@huonw huonw commented Mar 13, 2014

rustc: make stack traces print for .span_bug/.bug.

Previously a call to either of those to diagnostic printers would defer
to the fatal equivalents, which explicitly silence the stderr
printing, including a stack trace from RUST_LOG=std::rt::backtrace.

This splits the bug printers out to their own diagnostic type so that
things work properly.

Also, this removes the Ok(...) that was being printed around the
subtask's stderr output.

Previously a call to either of those to diagnostic printers would defer
to the `fatal` equivalents, which explicitly silence the stderr
printing, including a stack trace from `RUST_LOG=std::rt::backtrace`.

This splits the bug printers out to their own diagnostic type so that
things work properly.

Also, this removes the `Ok(...)` that was being printed around the
subtask's stderr output.
bors added a commit that referenced this pull request Mar 14, 2014
rustc: make stack traces print for .span_bug/.bug.

Previously a call to either of those to diagnostic printers would defer
to the `fatal` equivalents, which explicitly silence the stderr
printing, including a stack trace from `RUST_LOG=std::rt::backtrace`.

This splits the bug printers out to their own diagnostic type so that
things work properly.

Also, this removes the `Ok(...)` that was being printed around the
subtask's stderr output.
@bors bors closed this Mar 14, 2014
@bors bors merged commit edb6b02 into rust-lang:master Mar 14, 2014
@huonw huonw deleted the printier-rustc branch December 4, 2014 02:03
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