|
From: Stephen M.
|
>>>>> "JW" == Josef Weidendorfer <Jos...@gm...> writes: JW> On Monday 28 August 2006 15:03, Bryan Meredith wrote: BM> I agree that would be the best solution but how does one work out BM> the compiler, given the IR (or is it buried in the debug info BM> somewhere). JW> If there is full debug information, you should be able to extract JW> everything you need (e.g. return type of a function). AFAIK, JW> Valgrind currently does parse symbol tables and line debug info, JW> but not much more. It would be cool to have a debug info parser JW> for further info like type and variable name available for tools JW> (for DWARF format). As I think I mentioned a while ago, one existing codebase that provides this is our research group's "Fjalar" framework, a melding of Valgrind and the GNU binutils "readelf" DWARF parser that we've used for a couple of fairly heavyweight analyses that combine Valgrind-based dynamic tracking with close-to-complete source level information from the debugging information. Its approach isn't quite as elegant as extending Valgrind's existing DWARF parser to get the additional information you need, but it scores high on the "laziness" scale. For more details: http://pag.csail.mit.edu/fjalar/ -- Stephen |