While I have found /var/lib/systemd/coredump/* to be extremely useful when gdb doesn't give the right answers, I have not been able to figure out the rationale behind it and what existed before it, in the sysvinit world-view.
I came across this recently as I have been getting segmentation faults on some software but running them under gdb didn't get the desired output. Running through /var/lib/systemd/coredump/ found the lost files and was able to run coredumpctl on some of it while the rest was able to unarchive the lz4 files and run them gdb and get the backtraces.
Any history, rationale would be nice.
While man pages of systemd-coredump, coredumpctl and even journalctl provide clues as to how it is to be used, doesn't tell anything about the rationale or reasoning/history behind it.