https://gcc.gnu.org/bugzilla/show_bug.cgi?id=128270
--- Comment #1 from Aliaksei Kandratsenka <alkondratenko at gmail dot com> --- I see this was tagged as "wrong-debug". Technically accurate, but I would also like to point out this is not just "someone doesn't get right backtrace in GDB at couple instructions in rare-ish DRAP functions". This is .eh_frame stuff using at runtime. This is _crashing bug_. Because SIGPROF-based cpu profiles will occasionally backtrace from these locations (aw-backtrace is built to handle such issues; but most backtracers aren't).
