Displaying 4 results from an estimated 4 matches for "sig_pid".
Did you mean:
si_pid
2019 Aug 08
2
another bizarre thing...
...> where I am now).
OK, more information.
Found a recipe to cause systemtap to emit a line of text identifying the sender of the SIGKILL.
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())
unfortunately, it says the program is killing itself:
SIGKILL was sent to myprog (pid:12269) by myprog uid:1000
So,... now I'm wondering how one figures that out. nowhere in my source code does it explicitly raise any signal, much less SIGKILL.
So there must be some unde...
2019 Aug 07
0
another bizarre thing...
...t; is where I am now).
OK, more information.
Found a recipe to cause systemtap to emit a line of text identifying
the sender of the SIGKILL.
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())
unfortunately, it says the program is killing itself:
SIGKILL was sent to myprog (pid:12269) by myprog uid:1000
So,... now I'm wondering how one figures that out. nowhere in my
source code does it explicitly raise any signal, much less SIGKILL.
So there must be some unde...
2019 Aug 08
0
another bizarre thing...
...formation.
>
> Found a recipe to cause systemtap to emit a line of text identifying the sender of the SIGKILL.
>
> 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())
>
> unfortunately, it says the program is killing itself:
>
> SIGKILL was sent to myprog (pid:12269) by myprog uid:1000
>
> So,... now I'm wondering how one figures that out. nowhere in my source code does it explicitly raise any signal, much less SIGKI...
2019 Aug 06
13
another bizarre thing...
Hi all!
I'm stuck on something really bizarre that is happening to a product
I "own" at work. It's a C program, built on CentOS, runs on CentOs or
RHEL, has been in circulation since the early 00's, is in use at
hundreds of sites.
recently, at multiple customer sites it has started just going away.
no core file (yes, ulimit is configured), nothing in any of its
(several)