Thread angst in Windows

Ick, what are you really trying to do that you need this level of info? I don''t think there is a standard way to determine if a thread is blocked. You might be able to play games with GetThreadContext but there won''t be any guarantees.

I believe that SuspendThread is really only meant to be used by debuggers - at least I''ve never needed it.

-Mike

If you need to know that, threading hasn''t made your life any easier :p

To detect a stalled thread you can use global watch-dog counters. Each thread gets a global hole that it increments while it''s running (in lingo "kicks the dog"). Then you decide on a time-out, and if the watch-dog doesn''t twiddling in that time-out perdio you assume it has stalled.

What technique/API(s) are you using for syncronization (i.e. are you calling WaitForSingleObject etc. to obtain a lock on a semaphore)?

I guess I''ll clarify why I need this information a bit more. What I''m working on is a research project to see what possible benefits could be found by applying a few different Real-time scheduling algorithms to interactive multimedia applications (games being one, but not the only, example of this.) So what I need to write is my own thread manager that will be responsible for managing the threads belonging to the tasks that it is given. Because I''m working on a reusable API, I won''t know for sure what kind of synchronization methods the application will use, so I can''t rely on any of that information. I may be able to adapt the watchdog approach, but I''m not sure if it would be the most efficient. If I can''t get that to work, I''ll post something new with more details about the specific situation

Thanks