forked from iovisor/bcc
-
Notifications
You must be signed in to change notification settings - Fork 0
/
killsnoop_example.txt
41 lines (30 loc) · 1.37 KB
/
killsnoop_example.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
Demonstrations of killsnoop, the Linux eBPF/bcc version.
This traces signals sent via the kill() syscall. For example:
# ./killsnoop
TIME PID COMM SIG TPID RESULT
12:10:51 13967 bash 9 13885 0
12:11:34 13967 bash 9 1024 -3
12:11:41 815 systemd-udevd 15 14076 0
The first line showed a SIGKILL (9) sent from PID 13967 (a bash shell) to
PID 13885. The result, 0, means success.
The second line showed the same signal sent, this time resulting in a -3
(ESRCH: no such process).
USAGE message:
# ./killsnoop -h
usage: killsnoop [-h] [-x] [-p PID] [-T PID] [-s SIGNAL]
Trace signals issued by the kill() syscall
optional arguments:
-h, --help show this help message and exit
-x, --failed only show failed kill syscalls
-p PID, --pid PID trace this PID only which is the sender of signal
-T TPID, --tpid TPID trace this target PID only which is the receiver of
signal
-s SIGNAL, --signal SIGNAL
trace a signal or a signal list
examples:
./killsnoop # trace all kill() signals
./killsnoop -x # only show failed kills
./killsnoop -p 181 # only trace PID 181
./killsnoop -T 189 # only trace target PID 189
./killsnoop -s 9 # only trace signal 9
./killsnoop -s 9,15 # trace signal 9 and 15