V Wed, Jan 31, 2024 at 01:07:42PM +0100, Milan Crha napsal(a): > evolution-3211 [003] d..1. 355.904404: signal_generate: sig=9 errno=0 code=128 comm=evolution pid=3211 grp=1 res=0 > evolution-3211 [003] d..2. 355.904450: signal_generate: sig=9 errno=0 code=0 comm=bwrap pid=3257 grp=1 res=0 > Key information is code=128. That code is probably si_code member described in sigaction(2). The manual lists a lot of values as constants. 128 value is SI_KERNEL according to /usr/include/asm-generic/siginfo.h. It is documented as "sent by the kernel from somewhere". It means the first signal does not come a user space. It's genuinly generated by kernel. E.g. when the process is killed for out-of-memory reason. However, in this case, I would expect kernel to log this event into dmesg. E.g. out-of-memory killer is very verbose in dmesg. Strange thing is the second line. It reads that process 3211 (code=0 meads SI_USER, "sent by kill, sigsend, raise") sent SIGKILL to 3257. It's questionable how a process 3211 killed with the first signal can still emit signals. A possible explanation is that the signals are procecessed asychnously and evolution manages to dispatch the signal to bwrap before kernel termites evolution because of the first signal. Or I misinterpret the log. -- Petr
Attachment:
signature.asc
Description: PGP signature
-- _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
