Requests that the common language runtime (CLR) create an iterator for the host to use to determine the set of tasks waiting on a reader-writer lock.
CreateRWLockOwnerIterator returned successfully.
The CLR has not been loaded into a process, or the CLR is in a state in which it cannot run managed code or process the call successfully.
The call timed out.
The caller does not own the lock.
An event was canceled while a blocked thread or fiber was waiting on it.
An unknown catastrophic failure occurred. When a method returns E_FAIL, the CLR is no longer usable within the process. Subsequent calls to hosting methods return HOST_E_CLRNOTAVAILABLE.
CreateRWLockOwnerIterator was called on a thread that is currently running managed code.
Hosts typically call the CreateRWLockOwnerIterator, DeleteRWLockOwnerIterator, and GetRWLockOwnerNext methods during deadlock detection. The host is responsible for ensuring that the reader-writer lock is still valid, because the CLR makes no attempt to keep the reader-writer lock alive. Several strategies are available for the host to ensure the validity of the lock:
The host can block release calls on the reader-writer lock (for example, IHostSemaphore::ReleaseSemaphore) while ensuring that this block does not cause deadlock.
The host can block the exit from waiting on the event object associated with the reader-writer lock, again ensuring that this block does not cause deadlock.
CreateRWLockOwnerIterator must be called only on threads that are currently executing unmanaged code.
Platforms: See .NET Framework System Requirements.
Library: Included as a resource in MSCorEE.dll
.NET Framework Versions: Available since 2.0