12 ms·
Thanks so much! You are right! Hopefully these formats will become standard and implemented in more toolchains. My worry is that there seem to be several "comp
by javierhonduco 4y ago
Thanks so much!
You are right! Hopefully these formats will become standard and implemented in more toolchains. My worry is that there seem to be several "competing" formats for a more compact DWARF debug (as opposed to unwind) information. I hope this doesn't lead to more fragmentation of the ecosystem.
Definitely! I assume you work at Google, so most of your binaries probably have some crash handlers set up already, right? I find this very useful, and wish it were more commonplace. I really like Folly's implementation of this idea [0] that just requires a single line of code: `folly::symbolizer::installFatalSignalHandler()`
- scottlamb 4y ago> I assume you work at Google I did for a really long time. At a startup now. > so most of your binaries probably have some crash handlers set up already, right? Yes, there was nice instrumentation there too. All google3 binaries did something like InitGoogle() that set off commandline flag parsing, signal handler installation, log hooks, mlock/huge page setup, etc.