Re: [Valgrind-developers] ThreadIds strange behavior.

SourceForge Headquarters 1320 Columbia Street Suite 310 San Diego, CA 92101 +1 (858) 422-6466

In message <42E...@si...>
          Augusto Vega <aug...@si...> wrote:

> <body bgcolor="#ffffff" text="#000000">
> I've noticed some strange behavior getting the current tid in a tool
> I'm building.<br>

Plain text would be appreciated...

> I've some C helpers, which are called from instrumentation code. Inside
> helpers, I call VG_(get_running_tid), which always return thread ids
> between 1 and 3 (never mind how many pthreads the client program had).

What version of valgrind are we alking about here?

> I thought it was some problem with VG_(get_running_tid), so I
> registered (in my tool) a callback function to be notified (from core)
> on thread switchings. But, the same problem occurs.

If that's the thread_run event then note that it wasn't being called
in the valgrind 3 code until the other day.

> I think that (valgrind) threads could be merged into (kernel)
> threads.... but I'm not sure about this (kernel threads are transparent
> to Valgrind, isn't it?)

I think don't I understand this. What do mean by 'merging' the
threads exactly?

Tom

-- 
Tom Hughes (to...@co...)
http://www.compton.nu/