On Wed, 2024-01-31 at 12:19 +0100, Petr Pisar wrote:
> This procedure works for me
> <https://stackoverflow.com/questions/2827877/tracing-unix-signal-origins>.
> The tracefs file system has a nice log.
Hi,
that works pretty well, thank you. Funny enough, if I read it
correctly, it says evo killed itself (the first three bwrap-s are
probably unrelated, it could be when I opened and closed a composer,
which let WebKitGTK create a new WebKitWebProcess; the last line might
be when WebKitGTK cleans up after itself, or all the bwraps are at last
created by the WebKitGTK):
bwrap-3756 [002] d..2. 341.677197: signal_generate: sig=9 errno=0
code=0 comm=bwrap pid=3757 grp=1 res=1
bwrap-3753 [000] d..2. 341.677296: signal_generate: sig=9 errno=0
code=0 comm=bwrap pid=3754 grp=1 res=1
bwrap-3856 [002] d..2. 345.231590: signal_generate: sig=9 errno=0
code=0 comm=bwrap pid=3857 grp=1 res=1
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
In such case, I might be able to catch this in gdb, right? Maybe with a
breakpoint in the `kill` function, and any other? These things are very
low-level for me, I'm sorry.
Bye,
Milan
--
_______________________________________________
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
