https://sourceware.org/bugzilla/show_bug.cgi?id=27666
--- Comment #1 from Rainer Orth <ro at CeBiTec dot Uni-Bielefeld.DE> --- When I tried a sparcv9-sun-solaris2.11 build of gdb master in preparation for the upcoming GDB 11 release, I found that the impact of this bug is way greater than just a couple of binutils testsuite failures: it causes many hundreds of gdb testsuite failures due to the same ambiguity: (gdb) break increment Breakpoint 1 at 0x100020368: file /vol/src/gnu/gdb/hg/master/dist/gdb/testsuite/gdb.ada/O2_float_param/callee.adb, line 19. (gdb) run Starting program: /vol/obj/gnu/gdb/gdb/11.4-sparcv9-dist/gdb/testsuite/outputs/gdb.ada/O2_float_param/foo warning: Unable to find dynamic linker breakpoint function. GDB will be unable to debug shared library initializers and track explicitly loaded dynamic code. Error while mapping shared library sections: `/lib/64/libc.so.1': not in executable format: file format is ambiguous Error while mapping shared library sections: `/lib/sparcv9/ld.so.1': not in executable format: file format is ambiguous As with binutils, reverting just the bfd/config.bfd part of the patch returns gdb testresults back to normal. Unless there's a considerably better (and sufficiently safe) alternative, this is what I believe should be done. -- You are receiving this mail because: You are on the CC list for the bug.
