https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66368
--- Comment #6 from boger at us dot ibm.com --- I think you've said the problem only occurs when using -fstack-protector-strong and when building with glibc-2.21. Have you tried using gdb to see where the segv actually occurs? >gdb go ..... >run version (Once it hits the segv) >x/20ni $pc-24 >bt The panic stacktrace is showing a line in proc.c:2328 which is making a call to __builtin_return_address according to my source. Does that match your source? If that is the case then I have a feeling this isn't go specific, but a problem with calling __builtin_return_address on ppc32 when using -fstack-protector-strong and possibly glibc-2.21 has some affect.
