https://sourceware.org/bugzilla/show_bug.cgi?id=33153
--- Comment #9 from Rainer Orth <ro at CeBiTec dot Uni-Bielefeld.DE> --- "ro at CeBiTec dot Uni-Bielefeld.DE" > --- Comment #8 from Rainer Orth <ro at CeBiTec dot Uni-Bielefeld.DE> --- [...] >>> However, there are quite a number of regressions in the binutils >>> testsuite: >> >> I suspect/hope that these are due to an unrelated issue. > > It is, as I've now discovered. In the unpatched tree, ld-ctf tests were > UNSUPPORTED since even a simple link test failed. With that problem > gone, the tests will run and FAIL. In the past, I repeated had problems > with CTF tests on Solaris that went away when mmap support was disabled > for libctf. I'll keep looking what's going on here... I've confirmed the mmap issue now. In fact, I'd already reported the issue 3 years ago in PR libctf/29292. I've finally reduced it to a small testcase that works everywhere but Solaris 11.4 (10 and 11.3 are ok). I've filed a bug with Oracle now, but the question remains why libctf does such a complicated mmap/msync/munmap dance here, just to avoid writing a 72-byte .ctf header directly. ISTM that one either should disable the use of mmap in libctf or rip out the mmap path completely. >>> I've not yet found what's wrong here, however it seems to be CTF related >>> in some way: >>> >>> exited abnormally with 1, >>> output:/var/gcc/binutils/i386/obj/binutils-2.45-branch/ld/../binutils/ >>> objdump: error: ctf_arc_bufopen(): cannot open CTF >>> /var/gcc/binutils/i386/obj/binutils-2.45-branch/ld/../binutils/objdump: CTF >>> open failure: Buffer does not contain CTF data. >>> /var/gcc/binutils/i386/obj/binutils-2.45-branch/ld/../binutils/objdump: >>> tmpdir/dump: file format not recognized -- You are receiving this mail because: You are on the CC list for the bug.
