Hacker News Reader

> non-goals (e.g., "make it easy to attach debuggers to apps replicated a zillion times in Borg")

But wouldn't it still be nice to have a standardized way to analyze post-mortem dumps across languages?

Google's anointed production languages used to be five: C++, Java, JavaScript, Python, and Go. Not much to reasonably standardize across, especially if a standardized solution ends up with more compromises than a custom one.

But DWARF uses less space than Go's native format. So inventing a custom "linetab" format seems like the compromise, not using DWARF.

I suspect that the format is again copy-pasted from somewhere in Plan9, and existing Plan9 tools for it are ported, too.

Insert standardization XKCD. It's been tried. And even so, you can still use the "standard" coredump tool to analyze a Go program's coredump with decent success.

It’s not fun, usually.

Reply on news.ycombinator.com