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

mention rust_panic in default panic! message #11704

Closed
pnkfelix opened this issue Jan 21, 2014 · 1 comment · Fixed by #30402
Closed

mention rust_panic in default panic! message #11704

pnkfelix opened this issue Jan 21, 2014 · 1 comment · Fixed by #30402

Comments

@pnkfelix
Copy link
Member

Rust developers are developers. Many will be used to using a debugger. Lets tell them straight up from the panic! message how they can hook up their debugger without having to know anything about rust's name mangling algorithm.

@alexcrichton alexcrichton changed the title mention rust_fail in default fail! message mention rust_panic in default panic! message Aug 17, 2015
@ranma42
Copy link
Contributor

ranma42 commented Jan 11, 2016

Used as workaround in #30625, but still discovered from other people instead of documentation.
#30625. Mentioning rust_panic in the panic message and possibly in the documentation for panic! might be a good idea. If nobody is already doing this, I will :)

bors added a commit that referenced this issue Jan 26, 2016
This splits the output of panics into two lines as proposed in #15239 and adds a
note about how to get a backtrace. Because the default panic message consists of
multiple lines now, this changes the test runner's failure output to not indent
the first line anymore.

Fixes #15239 and fixes #11704.
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 a pull request may close this issue.

3 participants