Skip to content
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

Rust never lets you know about RUST_BACKTRACE=full #41584

Closed
CryZe opened this issue Apr 27, 2017 · 3 comments
Closed

Rust never lets you know about RUST_BACKTRACE=full #41584

CryZe opened this issue Apr 27, 2017 · 3 comments

Comments

@CryZe
Copy link
Contributor

CryZe commented Apr 27, 2017

Ever since RUST_BACKTRACE got split up into a short and full backtrace, there used to be a message that tells you about the full backtrace when you are seeing the shortened one. The message however only comes up when stack frames are omitted See here. This used to be the case for the shortened backtrace, but since the frame pruning logic got reverted by #41364, this message is now dead code until frame pruning is implemented again (#40264). However it might also make sense to just always show this message for a short backtrace instead of counting the amount of omitted frames.

@petrochenkov
Copy link
Contributor

If no frames are omitted, then full and short backtraces are equivalent.
No reason to spend people's time and recommend using full if the result will be the same.

@CryZe
Copy link
Contributor Author

CryZe commented Apr 27, 2017

The short backtrace hides other information like the addresses and the function hashes though.

@CryZe
Copy link
Contributor Author

CryZe commented Apr 27, 2017

Looks like it's intentional, so I'm closing this.

@CryZe CryZe closed this as completed Apr 27, 2017
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

No branches or pull requests

2 participants