StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
1947524
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2009-12-22T16:35:07.773
FavoriteCount
0
LastActivityDate
2012-03-16T11:49:17.687
LastEditDate
2012-03-16T11:49:17.687
LastEditorUserId
520044
OwnerUserId
118939
ParentId
1947312
PostTypeId
2
Score
4
ViewCount
0
LastEditorDisplayName
text
Body
<p>I don't think there is a trivial way to resolve the actual owner of a Mutex, but the process that owns it can create other secondary items whose lifetimes are tied to it. There are plenty of mechanisms that are suitable for calling back across-process without having a main window.</p> <ol> <li>Register an object in the COM Running Object Table. Clients that are unable to take ownership of the Mutex can lookup the owner via the ROT and call back to the owner. A File Moniker should be suitable for registration here.</li> <li>Create a chunk of shared memory containing location details for the owner process. From there, write into the buffer the process handle and thread handle of a thread that can receive windows messages, and then use PostThreadMessage() to send a notification. Any other competing process may open the shared memory for read-only to determine where to send a windows message.</li> <li>Listen in the owner process on a Socket or Named Pipe. Probably overkill and not a good match for your needs.</li> <li>Use a shared file with locking. I'm not fond of this because the owner will need to poll, and it won't gracefully handle N potential other processes that could be trying to contact the owner at the same time.</li> </ol> <p>Here are reference links for the first two options.</p> <ol> <li><a href="http://msdn.microsoft.com/en-us/library/ms695276%28VS.85%29.aspx" rel="nofollow noreferrer">IRunningObjectTable @ MSDN</a> , <a href="http://msdn.microsoft.com/en-us/library/ms688670%28VS.85%29.aspx" rel="nofollow noreferrer">File Monikers @ MSDN</a></li> <li><a href="http://msdn.microsoft.com/en-us/library/aa366551(v=VS.85).aspx" rel="nofollow noreferrer">Creating Named Shared Memory @ MSDN</a> </li> </ol>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POWin32: How to get the process/thread that owns a mutex?
  singulars
  PostTypePostTypeId
  PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. UStakrl
UserOwnerUserId
1. USmeklarian
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POWin32: How to get the process/thread that owns a mutex?
  singulars
  PostTypePostTypeId
  PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
  singulars
  PostPostId
  PO
  UserUserId
  This table or related slice is empty.
  VoteTypeVoteTypeId
  VTUpMod
2. VO
  singulars
  PostPostId
  PO
  UserUserId
  This table or related slice is empty.
  VoteTypeVoteTypeId
  VTAcceptedByOriginator
3. VO
  singulars
  PostPostId
  PO
  UserUserId
  This table or related slice is empty.
  VoteTypeVoteTypeId
  VTApproveEditSuggestion
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.