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

can't call foreign function __libc_current_sigrtmin #2832

Closed
dead-claudia opened this issue Apr 6, 2023 · 1 comment · Fixed by #2837
Closed

can't call foreign function __libc_current_sigrtmin #2832

dead-claudia opened this issue Apr 6, 2023 · 1 comment · Fixed by #2837

Comments

@dead-claudia
Copy link

__libc_current_sigrtmax is present (and so I can use libc::SIGRTMAX() without issue), but not __libc_current_sigrtmin for some reason (preventing me from using libc::SIGRTMIN()).

I could easily shim this to 35 for practical testing purposes (kernel starts at 32, glibc reserves 3 for its threading library), but it'd be nice to not have to hack that in.

@RalfJung
Copy link
Member

Yeah that should be easy to add in Miri.

LegNeato added a commit to LegNeato/miri that referenced this issue Apr 11, 2023
bors added a commit that referenced this issue Apr 11, 2023
@bors bors closed this as completed in 28475a6 Apr 11, 2023
RalfJung pushed a commit to RalfJung/rust that referenced this issue Apr 28, 2023
RalfJung pushed a commit to RalfJung/rust that referenced this issue Apr 28, 2023
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.

2 participants