From: "Lavrentiev, Anton (NIH/NLM/NCBI) [C]" <lavr@ncbi.nlm.nih.gov>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: RE: Possible race in SYSV IPC (semaphores)
Date: Fri, 23 Nov 2012 17:47:47 +0000
Message-ID: <5F8AAC04F9616747BC4CC0E803D5907D0162E7@MLBXv04.nih.gov>
References: <5F8AAC04F9616747BC4CC0E803D5907D012856@MLBXV09.nih.gov> <20121123113605.GN17347@calimero.vinschen.de> <20121123131020.GR17347@calimero.vinschen.de> <20121123133332.GU17347@calimero.vinschen.de> <20121123164404.GX17347@calimero.vinschen.de> <5F8AAC04F9616747BC4CC0E803D5907D0162C6@MLBXv04.nih.gov> <20121123172937.GA12624@calimero.vinschen.de>
In-Reply-To: <20121123172937.GA12624@calimero.vinschen.de>
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Content-Transfer-Encoding: 8bit

> I agree.  I'll do that in the next couple of days.

Thank you.  Please let me know when you do, so that I can
check the relevant snapshot out.

Incidentally, have you been able to confirm the dead-locking
that I reported earlier (below)?  I just ran the patched cygserver
with the "-d -l 7" arguments, along with my test case, and both
dead-locked just as before.

> The test case attached from my earlier post from today, also shows
> a race (dead-lock, actually) occurring in CYGSERVER, when it is run
> with the "-d -l 7" command line (even when it is only one application,
> the test case is using it).  There is an internal disconcert between
> the cygserver threads.
> 
> The log ends with this, and there is no way to stop the server
> (like with "cygrunsrv -E") other than killing it from the task
> manager.

Anton Lavrentiev
Contractor NIH/NLM/NCBI