On Friday 22 February 2008 15:24, Bart Van Assche wrote: > On Fri, Feb 22, 2008 at 2:38 PM, Julian Seward <[EMAIL PROTECTED]> wrote: > > I am (very) surprised to hear that track_{start,stop}_client_code > > give wrong results. > > As soon as I have the time I will look further into this issue. But > please note that I have raised this issue more than once in the past > -- see e.g. http://bugs.kde.org/show_bug.cgi?id=152728.
Yes. I'm only saying that track_{start,stop}_client_code look correct to me, and so the problem is more likely to be elsewhere, perhaps: VG_(get_running_tid)() produces wrong results, under some circumstances, or the assertion that VG_(get_running_tid)() and track_{start,stop}_client_code agree is not always valid, for some subtle reason. I am a bit unclear about the precise semantics of VG_(get_running_tid) (was it ever specified, exactly? I don't know). That probably doesn't help. A first step might be to specify exactly the behaviour of this fn. 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