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

Signal should support arbitrary signals #1249

Open
joshtriplett opened this issue Jan 4, 2025 · 0 comments
Open

Signal should support arbitrary signals #1249

joshtriplett opened this issue Jan 4, 2025 · 0 comments

Comments

@joshtriplett
Copy link
Member

joshtriplett commented Jan 4, 2025

The Signal enum is missing the real-time signals, from SIGRTMIN to SIGRTMAX.

Handling these will be interesting, because glibc reserves the first two of them, and does so by changing its exposed value of SIGRTMIN.

I would suggest exposing the same SIGRTMIN that glibc does (34 rather than 32), and additionally exposing enum values for the two reserved signal numbers, with names that clearly indicate that they're reserved by libc.

That way, when people port from C to Rust, they won't get surprised by the difference.

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

No branches or pull requests

1 participant