elfutils-devel@xxxxxxxxxxxxxxxxxxxxxx is the place to post about your build issues. You're just in luck that I happen to be on this list too to have noticed. You probably need a newer automake or something and run "autoreconf -f -i"; I'm using 1.10.1 and autoconf-2.63. (Or you can just use the rpm/tarball instead of git, and not run auto* yourself.) For what you want I suspect that none of our stuff is the way to go about it, really. As acme pointed out, lots of that information is lost in compilation and is not really accessible any more. What we can do (and not at all easily any time soon) is rediscover some of it. But it's all there in the source, and I'm sure there are source-parsing tools that do what you want around to be found (cscope maybe? some IDE's features?). On the (unwritten) list for the future is doing something quite like what you asked about. But it's a far ways off, and, again, it's really almost certainly not the right way to skin your particular cat. What it is I have in mind for the future is a combination of a "smart disassembler" that generates DWARF location expressions describing instruction operands, with lots of general smarts for hacking location expressions. Then you could disassemble, analyze the DWARF describing the containing scope, and match up each instruction operand's location expression with the locations of variables in scope. One target use for this is to identify the "hot variables" (or hot struct fields) by identifying "hot spots" in the code via profiling etc., and then analyzing the locations are used in that code to yield the source constructs that correspond. I think this will be a fabulous thing. But it's a long ways off. And, it's not at all the most sensible or straightforward approach for addressing your case where plain source analysis would be much easier and more informative. Thanks, Roland -- To unsubscribe from this list: send the line "unsubscribe dwarves" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
