4 ms·
I don't know why this is downvoted. A crashdump would have made this 10x easier to debug. The answer is because "its linux" and crashdumps (except on a few di
by drewg123 5y ago
I don't know why this is downvoted. A crashdump would have made this 10x easier to debug.
The answer is because "its linux" and crashdumps (except on a few distros) are not part of the culture. These days linux actually kexec's another kernel with reserved physical memory to handle doing the dumps. This was absurdly hard to setup the last time I needed to do linux kernel debugging (years ago).
The linux kernel is generally compiled without frame pointers, and with other optimizations that are hostile to debugging.
We have kernel and userspace crashdumps enabled on our fleet of FreeBSD CDN servers, and having a real crashdump and not just a stack has been super helpful.
- uvdn7 5y agoI agree with you but we should leave frame pointer out of this — as it almost has nothing to do with it? libunwind knows how to read DWARF anyway. It’s more an implementation detail.