tags:

views:

2023

answers:

8

The title says it all. I didnt find any Win32 API which gives the state of a thread. So how do I get the Thread state?

A: 

You don't, unfortunately. Depending on your code, you could approximate this (by setting a flag whenever you wait on a kernel object for instance) but keep in mind that a thread could always block inside an OS or library call and you wouldn't know about it.

Peter Ruderman
A: 

In Windows 7, you can use QueryUmsThreadInformation. (UMS stands for User mode scheduling).

See here for UmsThreadIsSuspended.

Brian R. Bondy
Minimum client requirement: Windows 7 (64-bit only)
Marco van de Voort
Thanks, modified.
Brian R. Bondy
For pre Windows 7, I wonder what SuspendThread returns for an already suspended thread. Maybe you can check this way by temporarily suspending/resuming and checking the return values. Just an idea, might not work.
Brian R. Bondy
+1  A: 

WMI's Win32_Thread class has a ThreadState property, where 5: "Suspended Blocked" and 6:Suspended Ready.

You will need the Thread's Id to get the right instance directly (the WMI object's Handle property is the thread id).

EDIT: Given this PowerShell query:

gwmi win32_thread | group ThreadState

gives

Count Name  Group
----- ----  -----
    6 2     {, , , ...}
  966 5     {, , , ...}

WMI has a different definition of "Suspended" to Win32.

Richard
+5  A: 

I think - originally - this information was not provided because any API that provided this info would be misleading and useless.

Consider two possible cases - the current thread has suspended the thread-of-interest. Code in the current thread knows about the suspended state and should be able to share it so theres no need for the kernel team to add an API.

The 2nd case, some other / a 3rd thread in the system has suspended the thread of interest (and theres no way to track which thread that was). Now you have a race condition - that other thread could, at any time - unsuspend the thread of interest and the information gleaned from the API is useless - you have a value indicating the thread is suspended when it is in fact, not.

Moral of the story - if you want to know that a thread is suspended - suspend it: The return value from SuspendThread is the previous suspend count of the thread. And now you DO know something useful - The thread WAS AND STILL IS suspended - which is useful. Or that it WASN't (but now is) suspended. Either way, the thread's state is now deterministically known so you can in theory make some intelligent choices based on that - whether to ResumeThread, or keep it suspended.

Chris Becke
Yep - any attempt to query the thread suspend state is going to be inherently racy
Paul Betts
There are thread states beyond "suspended" and "running." I think it's more likely that the OP is interested in knowing which threads are blocked. In any case, your point about race conditions is a good one. If there is a way to get a thread's state, it should be used only for informational purposes. Any attempt to use it for control flow will lead to a world of hurt.
Peter Ruderman
Exactly - suspended or not suspended is typically not of interest. Running or waiting on a synchronisation signal.... that is typically what is of interest, and is clearly something that can be determined since debuggers and tools such as Performance Monitor surface precisely this information. Furthermore in a properly written application, threads will *never* be suspended unless running under a debugger.
Deltics
A: 

you could get thread suspend count with code like this:

DWORD GetThreadSuspendCount(HANDLE hThread) {
    DWORD dwSuspendCount = SuspendThread(hThread);
    ResumeThread(hThread);
    return dwSuspendCount;
}

but, as already said - it is not accurate. Moreover, suspending a thread is evil.

Andrey
A: 

I think the state here is referred to as

  • If thread is in thread proc , doing some processing Or
  • Waiting for event

This can be taken care of by using variable which can tell that if a thread is actually running or waiting for event to happen.

These scenarios appear when considering threadpools, having some n threads and based on each thread running status , tasks can be assigned to idle threads.

Alien01
A: 

Hi dear friends , i have read all chances.

but my requirement is not metting this in no way.

i want to get the state of a Win32 thread running in visual Studio Exe in Windows Xp.

apart from suspended / running , i need to know other states of a thraed ie , waiting or ready etc as per the scheduler architecture exactly in an RTOS design

Renjith G
A: 

You can get this information by calling NtQuerySystemInformation() with the value for SystemProcessesAndThreadsInformation (integer value 5).

If you want an example of what you can do with this information take a look at Thread Status Monitor.

Stephen Kellett