From: fche@redhat.com (Frank Ch. Eigler)
To: kernelnewbies@lists.kernelnewbies.org
Subject: monitor of SEGFAULT processes
Date: Thu, 16 Mar 2017 10:55:26 -0400 [thread overview]
Message-ID: <y0m1stxp8yp.fsf@fche.csb> (raw)
In-Reply-To: <1351991489645397@web55g.yandex.ru> (Lev Olshvang's message of "Thu, 16 Mar 2017 09:23:17 +0300")
levonshe wrote:
> [...] Is it possible from kernel module or user space to monitor
> which processes were terminated abnormally ? [...]
Depending on the version & configuration, there exist both kernel
tracepoints and kprobe/jprobe sites where the kernel side of these
events may be hooked. You may be able to attach to each of those from
userspace via perf.
For comparison, systemtap chooses whatever facility is available in your
kernel, by internally mapping the abstract "signal.send" name into a
list of candidates.
# stap -e '
probe signal.send {
if (sig_name == "SIGKILL")
printf("%s was sent to %s (pid:%d) by %s uid:%d\n",
sig_name, pid_name, sig_pid, execname(), uid())
}'
- FChE
prev parent reply other threads:[~2017-03-16 14:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-16 6:23 monitor of SEGFAULT processes Lev Olshvang
2017-03-16 14:55 ` Frank Ch. Eigler [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=y0m1stxp8yp.fsf@fche.csb \
--to=fche@redhat.com \
--cc=kernelnewbies@lists.kernelnewbies.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).