1PROBE::SIGNAL.SEND(3stap) Signal Tapset PROBE::SIGNAL.SEND(3stap)
2
3
4
6 probe::signal.send.return - Signal being sent to a process completed
7 (deprecated in SystemTap 2.1)
8
10 signal.send.return
11
13 send2queue
14 Indicates whether the sent signal was sent to an existing sigqueue
15
16 name
17 The name of the function used to send out the signal
18
19 retstr
20 The return value to either __group_send_sig_info,
21 specific_send_sig_info, or send_sigqueue
22
23 shared
24 Indicates whether the sent signal is shared by the thread group.
25
27 The signal's sender. (correct?)
28
30 Possible __group_send_sig_info and specific_send_sig_info return values
31 are as follows;
32
33 0 -- The signal is successfully sent to a process, which means that,
34 (1) the signal was ignored by the receiving process, (2) this is a
35 non-RT signal and the system already has one queued, and (3) the signal
36 was successfully added to the sigqueue of the receiving process.
37
38 -EAGAIN -- The sigqueue of the receiving process is overflowing, the
39 signal was RT, and the signal was sent by a user using something other
40 than kill.
41
42 Possible send_group_sigqueue and send_sigqueue return values are as
43 follows;
44
45 0 -- The signal was either successfully added into the sigqueue of the
46 receiving process, or a SI_TIMER entry is already queued (in which
47 case, the overrun count will be simply incremented).
48
49 1 -- The signal was ignored by the receiving process.
50
51 -1 -- (send_sigqueue only) The task was marked exiting, allowing *
52 posix_timer_event to redirect it to the group leader.
53
55 tapset::signal(3stap)
56
57
58
59SystemTap Tapset Reference May 2019 PROBE::SIGNAL.SEND(3stap)