Skip to content

Clarify order of signal handler execution for .NET 10 #11439

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.

Sign up for GitHub

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

Merged
merged 1 commit into from
Jun 25, 2025
Merged

Clarify order of signal handler execution for .NET 10 #11439

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions xml/System.Runtime.InteropServices/PosixSignalRegistration.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -82,6 +82,7 @@ Raw values can be provided for `signal` on Unix by casting them to <xref:System.
<xref:System.Runtime.InteropServices.PosixSignal.SIGINT> and <xref:System.Runtime.InteropServices.PosixSignal.SIGQUIT> can be canceled on both
Windows and on Unix platforms; <xref:System.Runtime.InteropServices.PosixSignal.SIGTERM> can only be canceled on Unix.
On Unix, terminal configuration can be canceled for <xref:System.Runtime.InteropServices.PosixSignal.SIGCHLD> and <xref:System.Runtime.InteropServices.PosixSignal.SIGCONT>.
In .NET 10 and later versions, the handlers are executed in reverse order of their registration.

]]></format>
</remarks>
Expand Down