Hi,
I came across an old mail thread in this forum which
discussed memory consumption overhead in helgrind.
http://www.mail-archive.com/valgrind-developers@lists.sourceforge.net/msg01905.html.
I was wondering whether, instead of tracking all data
addresses, how badly a tool which does the tracking of
locksets based on PC addresses for load/store accesses
would do? Though such a mechanism can have plenty of
false positives (due to same piece of code used for
accessing different data, such as updating a linked
list for different kinds of list, with different
locks) and false negatives as well. But such a rough
tool can serve as a first pass for pruning the
candidates for a tool using lockset discipline on data
addresses. Has there been any previous tool which may
have tried this approach?
The reason for thinking that such a pass may reduce
memory consumption is we donot need to track whole
linked lists etc when the list is protected always by
same lock for all its elements, and hence we donot
need to track all addresses in the list.
Another thought was whether the switch from tracking
locking discipline based on PC addresses to data
addresses can be made on the fly. Ie.once a PC
location is accessed with a different incoming thread
lockset from the candidate lockset,we can start
tracking that data address of that memory access as
normally being done for any lockset based detector
such as helgrind.
Thanks!
sandya
____________________________________________________________________________________
Never miss a thing. Make Yahoo your home page.
http://www.yahoo.com/r/hs
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Valgrind-developers mailing list
Valgrind-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/valgrind-developers
