Re: systemd243rc2, sysd-coredump is not triggered on segfaults

[Michael Chapman <mike@xxxxxxxxxxxxxxxxx>]

On Tue, 3 Sep 2019, Chris Murphy wrote:
> Maybe it's something unique to gnome-shell segfaults, that's the only
> thing I have crashing right now. But I've got a pretty good reproducer
> to get it to crash and I never have any listings with coredumpctl.
> 
> process segfaults but systemd-coredump does not capture it
> https://bugzilla.redhat.com/show_bug.cgi?id=1748145

GNOME shell appears to handle several normally-fatal signals, including 
SIGSEGV.

If I'm reading [1] correctly GNOME shell ignores all signals, dumps the 
GJS stack, and re-raises the signal. This will not work correctly for a 
user-generated SIGSEGV however... the signal generated by raise() will 
just get ignored. (If the kernel generates SIGSEGV it arranges things so 
the process is terminated even if SIGSEGV is ignored, I think.)

So I think this might be a GNOME shell bug.

[1] https://gitlab.gnome.org/GNOME/gnome-shell/blob/master/src/main.c#L366-403
_______________________________________________
systemd-devel mailing list
systemd-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.freedesktop.org/mailman/listinfo/systemd-devel