The answer, which is far more practical these days, given the proliferation of computers, is setup netconsole (to an RPi?), and get debug messages out of the kernel, assuming the crashed aren't MCE errors that are logged to bios and reported on bootup. The other bit to rail against, is closed source drivers and blobs. They'll crash the kernel, and debugging those are basically impossible.
While I agree with this, and I will end up troubleshooting the issue and figuring it out this week, it kinda proves my point. I would not need something like this in macOS.
On the other hand, if I did, I don't have the same troubleshooting power I would have with Linux. I guess /u/nkoren is right, computing in 2019 sucks.
It proves your point, but puts up a new one: netconsole isn't possible on OS X outside of Cupertino. I don't want to have to work at Apple to debug this issue that exists on Radar, outside of public view, but isn't reliably reproducible, and isn't even possible to fix in the next release OS X, or a custom kext.
