Missing unwind info in __startcontext was found that can lead to infinite loop in _Unwind_Backtrace. Generating stack trace in application code compiled with gccgo can trigger this, causing the affected process hanging up instead of error message. Upstream bug: https://sourceware.org/bugzilla/show_bug.cgi?id=20435
Created glibc tracking bugs for this issue: Affects: fedora-all [bug 1383298]
Affects only ARM EABI (32-bit) platforms.
Created glibc-arm-linux-gnu tracking bugs for this issue: Affects: fedora-all [bug 1383311]