SignalObjectAndWait
[New
- Windows NT]
The SignalObjectAndWait
function allows the caller to atomically signal an object and wait on another
object.
BOOL SignalObjectAndWait(
HANDLE hObjectToSignal, |
// handle
of object to signal |
HANDLE hObjectToWaitOn, |
// handle
of object to wait for |
DWORD dwMilliseconds, |
// time-out
interval in milliseconds |
BOOL bAlertable |
//
alertable flag |
); |
|
Parameters
hObjectToSignal
Specifies the
handle to the object to signal. This object can be a semaphore, a mutex, or an
event. If the handle is a semaphore, SEMAPHORE_MODIFY_STATE access is required.
If the handle is an event, EVENT_MODIFY_STATE access is required. If the handle
is a mutex, SYNCHRONIZE access is assumed, because only the owner of a mutex
may release it. For more information, see Interprocess Synchronization
Objects
hObjectToWaitOn
Specifies the
handle of the object to wait for. For a list of the object types whose handles
you can specify, see the Remarks section later in this topic.
dwMilliseconds
Specifies the
time-out interval, in milliseconds. The function returns if the interval
elapses, even if the object's state is nonsignaled and no completion or
asynchronous procedure call (APC) objects are queued. If dwMilliseconds
is zero, the function tests the object's state, checks for queued completion
routines or APCs, and returns immediately. If dwMilliseconds is
INFINITE, the function's time-out interval never elapses.
bAlertable
Specifies
whether the function returns when the system queues an I/O completion routine
or an APC for the calling thread. If TRUE, the function returns, and the thread
calls the completion routine or APC function. If FALSE, the function does not
return, and the thread does not call the completion routine or APC function.
Return Values
If the
function succeeds, the return value indicates the event that caused the
function to return.
If the
function fails, the return value is 0xFFFFFFFF. To get extended error
information, call GetLastError
Upon success,
the return value is one of the following values:
Value |
Meaning |
WAIT_ABANDONED |
The
specified object is a mutex object that was not released by the thread that
owned the mutex object before the owning thread terminated. Ownership of the
mutex object is granted to the calling thread, and the mutex is set to
nonsignaled. |
WAIT_IO_COMPLETION |
One or more
I/O completion routines or user-mode APCs are queued for execution. |
WAIT_OBJECT_0 |
The state
of the specified object is signaled. |
WAIT_TIMEOUT |
The
time-out interval elapsed, and the object's state is nonsignaled. |
Remarks
A completion
routine is queued for execution when the ReadFileEx
The SignalObjectAndWait
function can wait for the following objects:
Object |
Description |
Change
notification |
The FindFirstChangeNotification |
Console
input |
The handle
is returned by the CreateFile |
Event |
The CreateEvent |
Mutex |
The CreateMutex |
Process |
The CreateProcess |
Semaphore |
The CreateSemaphore |
Thread |
The CreateProcess |
Timer |
The CreateWaitableTimer |
You have to
be careful when using the wait functions and DDE. If a thread creates any
windows, it must process messages. DDE sends messages to all windows in the
system. If you have a thread that uses a wait function with no time-out
interval, the system will deadlock. Therefore, if you have a thread that
creates windows, use MsgWaitForMultipleObjects or MsgWaitForMultipleObjectsEx,
rather than SignalObjectAndWait.
See Also