Skip to content

Docs on bugreporting should elaborate on creating a stack trace #19745

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.

Sign up for GitHub

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

Jump to bottom
Closed
untitaker opened this issue Dec 11, 2014 · 1 comment
Closed

Docs on bugreporting should elaborate on creating a stack trace #19745

untitaker opened this issue Dec 11, 2014 · 1 comment

Comments

@untitaker
Copy link
Contributor

http://doc.rust-lang.org/complement-bugreport.html#what-information-should-i-include-in-a-bug-report?

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.

This doesn't explain anything to me, but a short added explanation probably won't suffice either.
@steveklabnik
Copy link
Member

This will end up being removed by #19738, which was just r+'d.

lnicola pushed a commit to lnicola/rust that referenced this issue May 20, 2025
@Veykril
Merge pull request rust-lang#19745 from Veykril/push-rnqulnqvltro
ad6f9f7 
minor: Add a mbe test for parsing negative literals
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@steveklabnik @untitaker