Skip to content

Commit 7eb2f59

Browse files
authored
Clarify order of signal handler execution for .NET 10 (#11439)
Follow up on dotnet/runtime#116557
1 parent 524c35b commit 7eb2f59

File tree

1 file changed

+1
-0
lines changed

1 file changed

+1
-0
lines changed

xml/System.Runtime.InteropServices/PosixSignalRegistration.xml

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -82,6 +82,7 @@ Raw values can be provided for `signal` on Unix by casting them to <xref:System.
8282
<xref:System.Runtime.InteropServices.PosixSignal.SIGINT> and <xref:System.Runtime.InteropServices.PosixSignal.SIGQUIT> can be canceled on both
8383
Windows and on Unix platforms; <xref:System.Runtime.InteropServices.PosixSignal.SIGTERM> can only be canceled on Unix.
8484
On Unix, terminal configuration can be canceled for <xref:System.Runtime.InteropServices.PosixSignal.SIGCHLD> and <xref:System.Runtime.InteropServices.PosixSignal.SIGCONT>.
85+
In .NET 10 and later versions, the handlers are executed in reverse order of their registration.
8586
8687
]]></format>
8788
</remarks>

0 commit comments

Comments
 (0)