On Tue, Oct 22, 2019 at 04:35:13AM -0700, Vito Caputo wrote: > On Tue, Oct 22, 2019 at 10:51:49AM +0000, Zbigniew Jędrzejewski-Szmek wrote: > > On Tue, Oct 22, 2019 at 12:34:45PM +0200, Umut Tezduyar Lindskog wrote: > > > I am curious Zbigniew of how you find out if the coredump was on a starved > > > process? > > > > A very common case is systemd-journald which gets SIGABRT when in a > > read() or write() or similar syscall. Another case is when > > systemd-udevd workers get ABRT when doing open() on a device. > > > > In the case of journald, is it really in read()/write() syscalls you're > seeing the SIGABRTs? I was sloppy here — it's not read/write, but various other syscalls. In particular clone(), which makes sense, because it involves memory allocation. Zbyszek _______________________________________________ systemd-devel mailing list systemd-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/systemd-devel