SyncManager.RecordThreadWaitingForLockMutex
- Updated2026-02-03
- 2 minute(s) read
SyncManager.RecordThreadWaitingForLockMutex
Syntax
SyncManager.RecordThreadWaitingForLockMutex( threadId, threadDisplayName, mutexName, mutexSyncMgr)
Purpose
Remarks
Do not call this method. This method is for internal use only to implement deadlock detection for mutex Synchronization objects.
Parameters
threadId As String
[In] Specifies a globally unique thread ID (GUID) for the thread performing the operation. When you call this method from a TestStand execution, specify the value of the Thread.UniqueThreadId property for this parameter. Because the TestStand Synchronization Manager permits sharing of mutexes between computers, you must use an ID more unique than just the current operating system thread ID of the current thread on the current computer. When you plan to use mutexes across computers, use a GUID or some other way of creating a thread ID that is unique across all computers. The Thread.UniqueThreadId property is a GUID.
threadDisplayName As String
[In] Specifies a display name to identify the current thread. This name is used to report any deadlock conditions that involve this thread.
mutexName As String
[In] Specifies a unique name for the Synchronization object. When the Synchronization object name begins with an asterisk, * , such as *syncobjectname , processes can share the object.
When the Synchronization object name begins with a computer name, such as \\computername\syncobjectname , you can share the object among computers, but the object resides on the computer for which you specify a name.
When the Synchronization object name begins with an asterisk or computer name, you can use a 32 or 64 prefix to specify using 32- or 64-bit TestStand to host the out-of-process Synchronization object. For example, the name 64*syncobj specifies a Synchronization object called *syncobj in the 64-bit TestStand host process, even when used from 32-bit TestStand. Use the prefix to share Synchronization objects between 32-bit TestStand and 64-bit TestStand in the same host process. If you do not use the prefix, 32-bit TestStand hosts out-of-process Synchronization objects in a 32-bit process, and 64-bit TestStand hosts out-of-process Synchronization objects in a 64-bit process.
mutexSyncMgr As SyncManager
[In] Specifies the TestStand Synchronization Manager associated with the mutex name.