|
From: | Joan Lledó |
Subject: | Re: pci arbiter being killed |
Date: | Sun, 7 Mar 2021 21:55:38 +0100 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.7.0 |
Hi El 7/3/21 a les 20:33, Samuel Thibault ha escrit:
Joan Lledó, le dim. 07 mars 2021 20:08:21 +0100, a ecrit:is not there any process that kills the arbiter after a while of not being used?That shouldn't be happening.and how could I know who is sending the SIGKILL?How do you notice that it's a SIGKILL?
I connected gdb to the arbiter and it showed a message saying the process has received a SIGKILL.
You could e.g. put mach_prints in glibc's sysdeps/mach/hurd/kill.c's SIGKILL case. Possibly better also add a mach_print in hurd/hurdsig.c SIGKILL on _hurd_orphaned.
I'll try that, thanks.
[Prev in Thread] | Current Thread | [Next in Thread] |