> not around all client memory accesses. There is a subtle difference: > e.g. before the code of a signal handler is executed, a signal context > is set up. track_start_client_code is invoked after the signal context > is set up and before the code of the signal handler is executed.
Ok good. So it's a semantics problem: 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. Are you intercepting both track_start_client_code and track_stop_client_code, or only the _start ? J ------------------------------------------------------------------------- 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
