https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64595
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jakub at gcc dot gnu.org
--- Comment #15 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
So do you only need .debug_line and some minimal .debug_info, or would
.debug_line be enough?
gdb understands e.g. .gnu_debuginfo format
http://fedoraproject.org/wiki/Features/MiniDebugInfo
which is essentially .xz compressed ELF in a section, containing just
.symtab/.strtab/.shstrtab. The wiki page says optionally .debug_line, but I
haven't found how that is produced. So perhaps you should produce something
like that for go binaries? Or just hack up dwarf2out.c, so in addition to
.debug_* sections it emits .gnu.go.debug_{line,abbrev,info} where the info
would only contain the absolute minimum of DWARF DIEs and attributes needed to
locate debug_line and find the ranges. Not being able to strip large debuginfo
sounds like a serious problem to me.
