|
From: Bryan O'S. <bo...@se...> - 2005-04-21 16:54:44
|
On Wed, 2005-04-20 at 22:41 -0500, Nicholas Nethercote wrote: > Valgrind's not really set up for mapping addresses to variables. The > meaning of "variable" is tricky when you're looking at binary code -- a > variable may be kept in memory, or the compiler could have put it into a > register, or a combination of the two. This kind of information is at least exposed, in principle, using DWARF location lists. Recent versions of gdb understand them, and recent versions of gcc emit them, so it's possible to reconstruct something like a "long long" properly, when part of it is in a register and part is in memory. I'm not suggesting that valgrind should care about this (though 'twould be nice), just noting that the information is there, at least when the stars are aligned appropriately. <b |