Skip to content

Bug report guide should mention RUST_BACKTRACE #19717

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
kmcallister opened this issue Dec 11, 2014 · 0 comments · Fixed by #19738
Closed

Bug report guide should mention RUST_BACKTRACE #19717

kmcallister opened this issue Dec 11, 2014 · 0 comments · Fixed by #19738
Labels
E-easy Call for participation: Easy difficulty. Experience needed to fix: Not much. Good first issue.

Comments

@kmcallister
Copy link
Contributor

The bug report guide says

Finally, if you can run the offending command under gdb, pasting a stack trace can be useful; to do so, you will need to set a breakpoint on rust_panic.

AFAIK, RUST_BACKTRACE=1 rustc ... will give equally useful information and doesn't require gdb.

@kmcallister kmcallister added A-docs E-easy Call for participation: Easy difficulty. Experience needed to fix: Not much. Good first issue. labels Dec 11, 2014
steveklabnik added a commit to steveklabnik/rust that referenced this issue Dec 11, 2014
brson added a commit to brson/rust that referenced this issue Dec 12, 2014
brson added a commit to brson/rust that referenced this issue Dec 15, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
E-easy Call for participation: Easy difficulty. Experience needed to fix: Not much. Good first issue.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant