This is an automated email from the ASF dual-hosted git repository. xiaoxiang781216 pushed a commit to branch master in repository https://gitbox.apache.org/repos/asf/nuttx.git
commit d093626b2b020b121cf612deb170b03119de5e14 Author: Marco Casaroli <[email protected]> AuthorDate: Thu Oct 22 12:42:27 2026 +0200 Documentation: Describe the pending signals of a thread and of a group. Say that a signal sent to one thread and a signal sent to the group are pending apart, and that the signals pending for a thread are discarded when it exits. Assisted-by: Claude Code:claude-opus-5-5 Signed-off-by: Marco Casaroli <[email protected]> --- Documentation/reference/user/07_signals.rst | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/Documentation/reference/user/07_signals.rst b/Documentation/reference/user/07_signals.rst index 05eb13bceff..ab7af3786fa 100644 --- a/Documentation/reference/user/07_signals.rst +++ b/Documentation/reference/user/07_signals.rst @@ -12,6 +12,13 @@ priority. The signal handler is a user-supplied function that is bound to a specific signal and performs whatever actions are necessary whenever the signal is received. +**Pending signals**. A signal that the receiver blocks stays pending +until the receiver unblocks it. A signal sent to the whole task group +(``kill()``) and a signal sent to one thread (``pthread_kill()``, +``tgkill()``) are pending apart: each target has at most one pending +instance of a signal that is not a real-time signal. The signals that +are pending for a thread are discarded when the thread exits. + By default, there are no predefined actions for any signal. The default action for all signals (i.e., when no signal handler has been supplied by the user) is to ignore the signal. In this sense, all NuttX are *real
