-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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
make clean on mac fails to cleanup *.dSYM directories #2215
Labels
E-easy
Call for participation: Easy difficulty. Experience needed to fix: Not much. Good first issue.
Comments
Yep, I get those, too. |
@brson can you think of any reasons not to change the rm lines to use -rf? |
@jdm nope, but let's limit the |
Fixt |
bors
added a commit
to rust-lang-ci/rust
that referenced
this issue
Sep 22, 2022
celinval
pushed a commit
to celinval/rust-dev
that referenced
this issue
Jun 4, 2024
RalfJung
pushed a commit
to RalfJung/rust
that referenced
this issue
Jun 29, 2024
…id_fixup-03, r=RalfJung Remove GetCurrentProcessId's frame_in_std check Most of the support required to close rust-lang#1727 was actually added a while back, in rust-lang#2215. However, for some reason, even though the Unix/Linux syscall equivalent has no `frame_in_std()` check, the Windows `GetCurrentProcessId` check did. While the vast majority of use cases use `std::process::id`, there's no particular reason to penalize any Windows code that is no_std or for whatever other reason choses to call the function directly (e.g. via the generated [windows-sys](https://docs.rs/windows-sys/latest/windows_sys/Win32/System/Threading/fn.GetCurrentProcessId.html) method). The emulation should still work fine. Given there's no reason not to, we might as well simplify the code a tiny bit and save that branch / frame check during runtime too. This PR removes the `frame_in_std` restriction for `GetCurrentProcessId`, and also moves it into the environment related shim section per discussion in rust-lang/miri#1727 (comment). Still passes existing tests/pass/getpid.rs test. Closes rust-lang#1727 unless we wish to give a dummy value when isolated, which we don't seem to want to do at this time.
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.
Lots of errors like:
The text was updated successfully, but these errors were encountered: