|
From: Bart V. A. <bar...@gm...> - 2006-08-11 06:50:31
|
Thanks for the hint, Nicholas. By this time I downloaded the Valgrind 2.2.0 sources (http://valgrind.org/downloads/valgrind-2.2.0.tar.bz2). I had a look at the functions VG_(describe_addr)(), VG_(get_scope_variables)(), and search_all_scopetabs(). I'm not familiar with DWARF or stabs details, and it's not clear to me how in how far these functions are specific to one specific debugging information format. None of these functions is present in Valgrind 3.2.0. Any idea how much work would it take to reintroduce these functions ? On 8/11/06, Nicholas Nethercote <nj...@cs...> wrote: > On Thu, 10 Aug 2006, Bart Van Assche wrote: > > > Regarding the drd (data-race detection) tool I'm working on: I > > have a question about how to obtain the name of a stack variable, > > given its address. > > Jeremy wrote a whole lot of complex code for reading debug info to get this > kind of info and more. It's certainly in Valgrind 2.2.0, it seems to have > been stripped out of 3.2.0, possibly because Helgrind has been broken for so > long. > > There was a function called VG_(describe_addr) in the file vg_symtypes.c in > 2.2.0. You might like to look at that, but it's pretty hairy. It also only > worked for stabs debug format, not DWARF. |