https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64595
--- Comment #13 from rguenther at suse dot de <rguenther at suse dot de> --- On Mon, 19 Jan 2015, ian at airs dot com wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64595 > > --- Comment #7 from Ian Lance Taylor <ian at airs dot com> --- > That failure is not related to the new gotools. I expect it would happen with > any Go program. Go requires that there be enough debug info to do a stack > backtrace with file/line information. It uses the libbacktrace library, but > that library doesn't understand separate debuginfo sections. > > I can fix this specific problem so that the program is more likely to run, but > in general Go code expects to be able to get that backtrace and most real Go > programs will fail without it. > > I guess I or somebody needs to fix libbacktrace to understand separate > debuginfo objects. Note that then gccgo should automatically enable -g, no? Because the only debuginfo present in a.out when compiling with gccgo is that of the crt?.o files. (yes, libgo is also stripped).
