|
From: janjust <tja...@un...> - 2012-10-07 01:16:48
|
Hey all,
Can a tid change during a single SB entry/exit?
If I get a running_tid() at SB_entry, does that hold for the rest of the
instrumented instructions in the same SB? If not, what is the likelyhood or
a scenario (if you can think of one) where that doesn't hold?
Thanks!
--
View this message in context: http://old.nabble.com/get_running_tid%28%29-tp34523374p34523374.html
Sent from the Valgrind - Users mailing list archive at Nabble.com.
|
|
From: John R. <jr...@bi...> - 2012-10-07 01:48:43
|
> Can a tid change during a single SB entry/exit? > If I get a running_tid() at SB_entry, does that hold for the rest of the > instrumented instructions in the same SB? If not, what is the likelyhood or > a scenario (if you can think of one) where that doesn't hold? There are two things that might happen: 1, that thread receives a signal, and during the signal handler there is a re-schedule which switches execution to a different thread. Maybe this isn't supposed to happen (because signals are handled only at end of block?), but ... 2. some other thread executes the same block in parallel. Today there can be no problem because execution is serialized. However there is work towards multi-threaded valgrind ... -- |