1PROBE::SIGNAL.SEND(3stap)        Signal Tapset       PROBE::SIGNAL.SEND(3stap)
2
3
4

NAME

6       probe::signal.send.return - Signal being sent to a process completed
7

SYNOPSIS

9       signal.send.return
10

VALUES

12       retstr
13           The return value to either __group_send_sig_info,
14           specific_send_sig_info, or send_sigqueue
15
16       send2queue
17           Indicates whether the sent signal was sent to an existing sigqueue
18
19       name
20           The name of the function used to send out the signal
21
22       shared
23           Indicates whether the sent signal is shared by the thread group.
24

CONTEXT

26       The signal's sender. (correct?)
27

DESCRIPTION

29       Possible __group_send_sig_info and specific_send_sig_info return values
30       are as follows;
31
32       0 -- The signal is sucessfully sent to a process,
33

WHICH MEANS THAT

35       (1) the signal was ignored by the receiving process, (2) this is a
36       non-RT signal and the system already has one queued, and (3) the signal
37       was successfully added to the sigqueue of the receiving process.
38
39       -EAGAIN -- The sigqueue of the receiving process is overflowing, the
40       signal was RT, and the signal was sent by a user using something other
41       than kill.
42
43       Possible send_group_sigqueue and send_sigqueue return values are as
44       follows;
45
46       0 -- The signal was either sucessfully added into the sigqueue of the
47       receiving process, or a SI_TIMER entry is already queued (in which
48       case, the overrun count will be simply incremented).
49
50       1 -- The signal was ignored by the receiving process.
51
52       -1 -- (send_sigqueue only) The task was marked exiting, allowing *
53       posix_timer_event to redirect it to the group leader.
54
55
56
57SystemTap Tapset Reference        August 2011        PROBE::SIGNAL.SEND(3stap)
Impressum