On Sun, Dec 27, 2015 at 03:16:48AM +0100, Mark Wielaard wrote: > On Sat, Dec 26, 2015 at 11:46:50PM +0100, Kurt Roeckx wrote: > > I finally uploaded the 0.164 version to Debian, but it's failing > > in the test suite on most arches with an error message like: > > dwfl_thread_getframes: no matching address range > > > > You can see a full log here: > > https://buildd.debian.org/status/fetch.php?pkg=elfutils&arch=powerpc&ver=0.164-1&stamp=1451167794 > > That is strange indeed. Especially since a somewhat similar test > run-backtrace-native.sh does seem to succeed. The output seems to > indicate that we cannot find the unwind (.eh_frame CFI) for raise > in this case. But there is not enough info to know for sure. > > Does the same test with 0.163 succeed on the same setup/arch? > If not, did glibc change between the last successful run and > the current failure on that architecture?
I didn't see that failure with 0.163. The last 0.163 upload was using glibc 2.19-19, the current version is 2.21-6. > You probably need access to a failing setup to debug a bit. > Most interesting would be to see whether or not the glibc.so > has CFI for raise and which addresses that covers. > $ eu-readelf --debug-dump=frame /lib/libc.so.6 | grep -4 '<raise>' > should give you a hint. That just returns: eu-readelf: cannot get debug context descriptor: No DWARF information found (I get that message on working systems too.) Without the grep it does return all kind of information, just nothing about raise. Both with a 2.19 and 2.21 libc6.so. Kurt
