Re: Figure out what killed an app (rhbz#2253099)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, 1 Feb 2024 at 09:13, Milan Crha <mcrha@xxxxxxxxxx> wrote:
> The kernel tracing log for sig==9 shows:
>
> gnome-terminal--2924    [002] dN.2.  2520.462889: signal_generate:
> sig=9 errno=0 code=128 comm=alloc-too-much pid=3502 grp=1 res=0
>
> There is no such thing (apart of the tracing log) when Evolution is
> suddenly killed, the logs are muted. That makes me believe it's not the
> OOM killer whom kills the application. I'm back at square 1; or maybe
> square 2, as I know possibly kernel sends it, but not why.

Try running `echo stacktrace >/sys/kernel/tracing/trace_options` (as
root) and then collect the kernel trace again. That should give you a
backtrace of kernel functions from the signal generation, which could
help you/us to figure out the reason the process was killed.
--
_______________________________________________
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




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux