|
From: Julian S. <js...@ac...> - 2005-07-29 17:52:05
|
> On Fri, 2005-07-29 at 14:12 +0100, Julian Seward wrote: > > > On Friday 29 July 2005 12:59, Duane Griffin wrote: > > > It builds and seems to work fine for me on AMD64 running SuSE 9.0, but > > > there are a number of failures in the regression test: > > > > > > == 157 tests, 35 stderr failures, 1 stdout failure ================= > > > > They are probably all encountering the same problem, but we'd need > > to see the nonempty <testname>.stderr.diff files to find out. Can you > > tar them up and send them? > > My pleasure, please find them attached. Looks like they are mostly just > caused by this warning: > > Warning: zero-sized CIE/FDE but not at section end in DWARF2 CFI reading Ok, all you DWARF2 CFA junkies out there :-), here's a question: I get the abovementioned warning a lot. Basically the call-frame unwinding information is a sequence of CIE or FDE records. What's in them doesn't matter, but each does have a size field which says how big that particular record is. Valgrind takes a zero-sized record as an end-of-sequence marker, and stops reading. Most of the time this corresponds to the end of the ELF .ehframe section, but sometimes it doesn't. For reference, "readelf --debug-dump=frames" also stops reading when it hits a zero-length CIE/FDE record. Problem is, the DWARF3 specification describes the CFA information in great detail, but it doesn't say how the end of the CIE/FDE record sequence is to be detected. If anybody can shed any light on this ultra-arcane point, I'd really appreciate it. J |