https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107675
--- Comment #9 from Tamar Christina <tnfchris at gcc dot gnu.org> --- (In reply to Florian Weimer from comment #8) > (In reply to Tamar Christina from comment #4) > > /opt/buildAgent/work/5c94c4ced6ebfcd0/libgcc/unwind-dw2-fde.c:111 > > #6 __register_frame_info (begin=<optimized out>, ob=0x48cfe8 <object>) at > > /opt/buildAgent/work/5c94c4ced6ebfcd0/libgcc/unwind-dw2-fde.c:150 > > #7 0x0000000000400798 in frame_dummy () at > > /opt/buildAgent/work/5c94c4ced6ebfcd0/libgcc/unwind-dw2-btree.h:361 > > #8 0x0000000000400f90 in __libc_csu_init () at > > /opt/buildAgent/work/5c94c4ced6ebfcd0/libgcc/unwind-dw2-btree.h:361 > > #9 0x0000000000400a78 in __libc_start_main () at > > /opt/buildAgent/work/5c94c4ced6ebfcd0/libgcc/unwind-dw2-btree.h:361 > > #10 0x0000000000400688 in _start () at > > /opt/buildAgent/work/5c94c4ced6ebfcd0/libgcc/unwind-dw2-btree.h:361 > > Looks like a build with USE_EH_FRAME_REGISTRY. Unless you have configured > with --explicit-exception-frame-registration=yes, it may mean that > USE_PT_GNU_EH_FRAME was not detected correctly. No, it's just made using default configure flags, no extra options.
