-
Notifications
You must be signed in to change notification settings - Fork 12.7k
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
check_unsafety: fix unused unsafe block duplication #45985
Conversation
@bors r+ |
📌 Commit bcaf685 has been approved by |
The duplicate error message is later removed by error message deduplication, but it still appears on beta and is still a bug
bcaf685
to
c0f7cce
Compare
📌 Commit c0f7cce has been approved by |
check_unsafety: fix unused unsafe block duplication The duplicate error message is later removed by error message deduplication, but it still appears on beta and is still a bug. r? @eddyb
💔 Test failed - status-travis |
Linker crashed (SIGBUS, not SIGSEGV) on macOS. cc @alexcrichton
We've got a crash log! Same as those reported in #38878 though. We're just going to change the fix in #40422 to handle SIGBUS as well and call it a day.
|
check_unsafety: fix unused unsafe block duplication The duplicate error message is later removed by error message deduplication, but it still appears on beta and is still a bug. r? @eddyb
☀️ Test successful - status-appveyor, status-travis |
Fix #38878 again — restart linker when seeing SIGBUS in additional to SIGSEGV. In #45985 (comment) we see a linker crashed due to Bus Error (signal 10) on macOS. The error was not caught by #40422 since the PR only handles Segmentation Fault (signal 11). The crash log indicates the problem is the same as #38878, so we just amend #40422 to include SIGBUS as well. (Additionally, modified how the crash logs are printed so that irrelevant logs are truly filtered out.)
The duplicate error message is later removed by error message
deduplication, but it still appears on beta and is still a bug.
r? @eddyb