On Fri, Feb 22, 2008 at 3:57 PM, Julian Seward <[EMAIL PROTECTED]> wrote:
> track_start/stop_client_code does only show you when the CPU is > running translated code blocks. However, it may be that a thread > has the CPU but is not running translated code, but instead doing > one of many other things (including building signal frames). > That's the difference: get_running_tid shows you what thread has > the CPU. In exp-drd I need the value of VG_(get_running_tid)() upon *every* client memory access, not just for the memory accesses generated by translated code. I would appreciate it very much that the Valgrind core would announce changes in VG_(get_running_tid)() instead of having to verify the value of VG_(get_running_tid)() in the tool. > Are you intercepting both track_start_client_code and track_stop_client_code, > or only the _start ? Only _start. Even if I would track _stop, I still would need code in the drd_trace_load() / drd_trace_store() functions for verifying whether VG_(get_running_tid)() changed. Bart. ------------------------------------------------------------------------- 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
