-
Notifications
You must be signed in to change notification settings - Fork 13.3k
Provide a option for mask local filesystem info from panic messages #40492
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
Conversation
Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @sfackler (or someone else) soon. If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes. Please see the contribution instructions for more information. |
Could you squash into a single commit? (This is only a personal preference.) In order to test you first need to be able to build. Under a Linux/macOS environment, IIRC, the following should be enough:
|
@estebank oops, I forget to run './configure'.
How?
After I run that command, I still couldn't build it up, it still something strange LLVM Compile Error. Let's try first clean it, then run it again. |
@kfairmasterz to squash the last
You'll want to change all but the last line to
After saving that, you'll be presented by git to edit the merged commit description. Just leave the description for the first commit. After this you can do |
@estebank Ouch, get more troubles now. Well, just let it go :P |
Strange build log:
|
No... Let's redo again |
It seems like the rebase might have gone awry :) As for the actual error, it is weird. Does it happen with a fresh clone of the repo as well? |
@estebank Just let me make a frash copy and then apply it =( |
@estebank Done. In finally, I have to generate a patch to apply and fixed problem =( |
@kfairmasterz no problem, squashing commits can be a pain. Are you still getting the original error? |
Stucking Edit: LLVM Compiling now. |
@@ -16,3 +16,6 @@ path = "../libcoretest/lib.rs" | |||
[[bench]] | |||
name = "corebenches" | |||
path = "../libcore/benches/lib.rs" | |||
|
|||
[features] | |||
mask_fileinfo_from_panic = [] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This should not as defaults.
@@ -39,3 +39,4 @@ debug-jemalloc = ["alloc_jemalloc/debug"] | |||
jemalloc = ["alloc_jemalloc"] | |||
force_alloc_system = [] | |||
panic-unwind = ["panic_unwind"] | |||
mask_fileinfo_from_panic = [] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This should not as defaults.
Compile failure log: http://paste.ubuntu.com/24174597/ I am tired for now. Getting some rest. And I have little confused, does |
r? @steveklabnik I have no idea who should I assign to. |
Can you spell out the motivation for this PR in more detail? |
@aturon Like what?
No, This is not like a reason. Well, It is time to say truth. =/
@aturon It is enough for the reason to merge this request? |
Thanks for clarifying @kfairmasterz. While we may eventually want a way to strip out these paths for the sake of bloat, the libs team felt that (1) it's not a high priority at this time and (2) it will take some deeper design. Thanks for the PR, but we're going to hold off for now. |
This is allowed someone who using xargo to compile and mask local system the source file info from many source
panic!
.It's only way to terminate that file path include binary from many source
panic!
.Original Issue: #40374
Thanks from https://internals.rust-lang.org/t/disabling-panic-handling/1834
By the way, Rust compiled binary is too large in some case if try to use the libstd.
I didn't test this Pull Request at all. I tried to run 'python x.py test src/libstd --stage 1`, then I got something about...