From mboxrd@z Thu Jan 1 00:00:00 1970 Content-Type: multipart/mixed; boundary="===============2207292117571022493==" MIME-Version: 1.0 From: Kurt Roeckx To: elfutils-devel@lists.fedorahosted.org Subject: Re: dwfl_thread_getframes: no matching address range Date: Sun, 27 Dec 2015 18:01:50 +0100 Message-ID: <20151227170150.GA16804@roeckx.be> In-Reply-To: 20151227164750.GC2790@blokker.redhat.com --===============2207292117571022493== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable On Sun, Dec 27, 2015 at 05:47:50PM +0100, Mark Wielaard wrote: > On Sun, Dec 27, 2015 at 01:26:59PM +0100, Kurt Roeckx wrote: > > > 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. > = > Does the test in 0.164 fail against glibc 2.19-19 on ppc? > Does the test in 0.163 succeed against glibc 2.21-6 on ppc? I will try this soon, but I'm probably going to test it against 2.19-18+deb8u1 which should be close enough to the -19 version I think. (Not sure I can install the 2.19-19 version myself.) > > > 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=3Dframe /lib/libc.so.6 | grep -4 '' > > > should give you a hint. > > = > > That just returns: > > eu-readelf: cannot get debug context descriptor: No DWARF information f= ound > > > > (I get that message on working systems too.) > = > That is just a warning because eu-readelf will try to print both .eh_frame > and .debug_frame information. It cannot find .debug_frame, but that > shouldn't be necessary in this case. > = > > Without the grep it does return all kind of information, just > > nothing about raise. Both with a 2.19 and 2.21 libc6.so. > = > That is surprising. I found libc6_2.21-6_powerpc.deb at > http://ftp.nl.debian.org/debian/pool/main/g/glibc/ > And indeed it doesn't seem to provide unwind info for "raise". > = > But I cannot find the 2.19-19_powerpc one there. Do you know where I > could find it, to compare? If you really want to test 2.19-19, it can be found at: http://snapshot.debian.org/archive/debian/20150710T034220Z/pool/main/g/glib= c/ > And if possible where to find the build logs of both and/or the > debuginfo packages? The libc6-dbg should be in the same directory in the pool. Build logs can be found at: https://buildd.debian.org/status/logs.php?pkg=3Delfutils&arch=3Dpowerpc Kurt --===============2207292117571022493==--