https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80914
--- Comment #7 from Steven Noonan <steven at uplinklabs dot net> --- With the compressed debug section support added to libbacktrace, gccgo will run fine when built using a binutils configured with --enable-compressed-debug-sections=all. However, programs built with that gccgo + binutils will crash: (Using the github.com/twstrike/ed448 go package as an example) $ go.gcc test -gccgoflags -Wl,--compress-debug-sections=none OK: 136 passed PASS ok github.com/twstrike/ed448 0.366s $ go.gcc test -gccgoflags -Wl,--compress-debug-sections=zlib fatal error: ranges offset out of range runtime stack: fatal error: ranges offset out of range panic during panic runtime stack: fatal error: ranges offset out of range stack trace unavailable exit status 4 FAIL github.com/twstrike/ed448 0.051s