On Sat, Nov 30, 2013 at 2:05 AM, Holger Eitzenberger <holger@xxxxxxxxxxxxxxxx> wrote: > > I am using gcc-go 4.8.2 on FC19, 32bit. > > When compiling even a simple program I sometimes get a segfault, which > goes away at the time I remove the optimizations: > > in ?? () from /lib/libgo.so.4 > #1 0xb7459b3d in backtrace_dwarf_add () from /lib/libgo.so.4 > #2 0xb745bd47 in ?? () from /lib/libgo.so.4 > #3 0xb745c0e1 in backtrace_initialize () from /lib/libgo.so.4 > > This is a bit annoying, as I am unable to do some performance > comparisons between Golang and C. > > Seems to be related with this [1] Debian bug report (GCC 4.7), from > October. > > Is this an issue which is fixed in GCC already? I think it is probably fixed by the patch in http://gcc.gnu.org/ml/gcc-patches/2013-10/msg01445.html . I will backport that patch to the 4.8 branch for inclusion with the future 4.8.3 release. Ian
