News for hackers. Stuff that matters.

A comment on Mid-stack inlining in the Go compiler. Parent comment

Re:Mid-stack inlining in the Go compiler by aclements on Monday March 06, 2017 @01:28PM (#13804813)
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.
[ Parent | on HN ]
Re:Mid-stack inlining in the Go compiler by CUViper on Monday March 06, 2017 @02:42PM (#13805433)
Isn't that what `.eh_frame` is for?
[ Parent | on HN ]
Re:Mid-stack inlining in the Go compiler by mnemonik on Monday March 06, 2017 @11:33PM (#13808299)
.eh_frame is DWARF with a couple tiny tweaks
[ Parent | on HN ]
Re:Mid-stack inlining in the Go compiler by CUViper on Tuesday March 07, 2017 @12:45PM (#13812674)
Right, but it's an allocated section that doesn't get stripped like debuginfo.
[ Parent | on HN ]