signal.send.return.3stap

Langue: en

Autres versions - même langue

Version: May 2009 (debian - 07/07/09)

Section: 3 (Bibliothèques de fonctions)

NAME

signal.send.return - Signal being sent to a process completed

SYNOPSIS

 signal.send.return 
 

VALUES

retstr

The return value to either <command>__group_send_sig_info</command>, <command>specific_send_sig_info</command>, or <command>send_sigqueue</command>

send2queue

Indicates whether the sent signal was sent to an existing <command>sigqueue</command>

name

The name of the function used to send out the signal

shared

Indicates whether the sent signal is shared by the thread group.

CONTEXT

The signal's sender. <remark>(correct?)</remark>

DESCRIPTION

Possible <command>__group_send_sig_info</command> and <command>specific_send_sig_info</command> return values are as follows;

<command>0</command> -- The signal is sucessfully sent to a process, which means that <1> the signal was ignored by the receiving process, <2> this is a non-RT signal and the system already has one queued, and <3> the signal was successfully added to the <command>sigqueue</command> of the receiving process.

<command>-EAGAIN</command> -- The <command>sigqueue</command> of the receiving process is overflowing, the signal was RT, and the signal was sent by a user using something other than <command>kill</command>.

Possible <command>send_group_sigqueue</command> and <command>send_sigqueue</command> return values are as follows;

<command>0</command> -- The signal was either sucessfully added into the <command>sigqueue</command> of the receiving process, or a <command>SI_TIMER</command> entry is already queued (in which case, the overrun count will be simply incremented).

<command>1</command> -- The signal was ignored by the receiving process.

<command>-1</command> -- (<command>send_sigqueue</command> only) The task was marked <command>exiting</command>, allowing * <command>posix_timer_event</command> to redirect it to the group leader.

AUTHOR

SystemTap

Hackers