Hacker News Reader

This is interesting work!

That said, it's a little disappointing when runtimes require custom algorithms or metadata to walk the stack and construct a stack trace. It makes it harder to build debuggers that grok the state of multiple runtimes (e.g., the Go code and the C code in the same program). This also affects runtime tracing tools like DTrace, which by construction can't rely on runtime support for help.

View on HN

We plan to expose all of the inlining information in the DWARF tables so debuggers won't have any problems with this. Internally, the runtime uses a different representation just so we can make it more compact and optimized for the runtime's exact needs. This way, you can also strip the debug info without breaking the runtime's own ability to walk stacks.

Isn't that what `.eh_frame` is for?

.eh_frame is DWARF with a couple tiny tweaks

Right, but it's an allocated section that doesn't get stripped like debuginfo.

The plan is to add inlining information to the DWARF tables so that debuggers and other tools can take advantage of it.

Reply on news.ycombinator.com