On 6/22/26 09:25, Karl Berry wrote:
[...]
P.S. Regarding core dumps, allow me to echo Bob F's comment: on some
systems (at least, every RHEL system I've ever seen), core dumps are
disabled by default. And it's not trivial to enable them. ulimit -c
does not suffice. What happens to core dumps is determined by
/proc/sys/kernel/core_pattern and on RHEL, that is set to
|/usr/lib/systemd/systemd-coredump %P %u %g %s %t %c %h %d %F
and I gave up on figuring out what happens after that. Core files don't
end up in the current directory, though, that's for sure.
Another systemd katamari "feature"...
Bottom line, for reliable tests, I think you cannot rely on a core file
being generated.
You never really could rely on core files to appear---unprivileged
ulimit -c cannot raise a hard limit and it was always possible for the
hard limit on core files to be set to zero.
To determine if the process was killed by a fatal signal, you must check
the exit code.
If you are concerned about a subprocess drawing a fatal signal, then you
need to patch the driver process to detect and report when its child
process dies by signal and have the test harness look for that error
report. This would also improve error reporting to users.
-- Jacob
