bcc-killsnoop(8)

1killsnoop(8)                System Manager's Manual               killsnoop(8)
2
3
4

NAME

6       killsnoop  -  Trace  signals  issued  by the kill() syscall. Uses Linux
7       eBPF/bcc.
8

SYNOPSIS

10       killsnoop [-h] [-x] [-p PID]
11

DESCRIPTION

13       killsnoop traces the kill() syscall, to  show  signals  sent  via  this
14       method.  This may be useful to troubleshoot failing applications, where
15       an unknown mechanism is sending signals.
16
17       This works by tracing the  kernel  sys_kill()  function  using  dynamic
18       tracing, and will need updating to match any changes to this function.
19
20       This  makes  use  of a Linux 4.4 feature (bpf_perf_event_output()); for
21       kernels older than 4.4, see the version under tools/old, which uses  an
22       older mechanism.
23
24       Since this uses BPF, only the root user can use this tool.
25

REQUIREMENTS

27       CONFIG_BPF and bcc.
28

OPTIONS

30       -h     Print usage message.
31
32       -x     Only print failed kill() syscalls.
33
34       -p PID Trace this process ID only (filtered in-kernel).
35
36       -s SIGNAL
37              Trace this signal only (filtered in-kernel).
38

EXAMPLES

40       Trace all kill() syscalls:
41              # killsnoop
42
43       Trace only kill() syscalls that failed:
44              # killsnoop -x
45
46       Trace PID 181 only:
47              # killsnoop -p 181
48
49       Trace signal 9 only:
50              # killsnoop -s 9
51

FIELDS

53       TIME   Time of the kill call.
54
55       PID    Source process ID
56
57       COMM   Source process name
58
59       SIG    Signal number. See signal(7).
60
61       TPID   Target process ID
62
63       RES    Result.  0  == success, a negative value (of the error code) for
64              failure.
65

OVERHEAD

67       This traces the kernel kill function and prints output for each  event.
68       As  the  rate  of  this  is generally expected to be low (< 100/s), the
69       overhead is also expected to be negligible. If you have an  application
70       that  is calling a very high rate of kill()s for some reason, then test
71       and understand overhead before use.
72

SOURCE

74       This is from bcc.
75
76              https://github.com/iovisor/bcc
77
78       Also look in the bcc distribution for a  companion  _examples.txt  file
79       containing example usage, output, and commentary for this tool.
80

OS

82       Linux
83

STABILITY

85       Unstable - in development.
86

AUTHOR

88       Brendan Gregg
89