X-Recipient:	archive-cygwin AT delorie DOT com
DomainKey-Signature:	a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:from:to:subject:date:message-id:references
	:in-reply-to:content-type:content-transfer-encoding
	:mime-version; q=dns; s=default; b=Gf7WuAzVIHfERDI0JX+Ywnm0GDa+k
	CXJDgiF7hZU4ZeVOtQ+ycEGSpe7dyt2uoAr0feoRvcGP8cSCNSAPFI2pFVtEKv31
	6EG7ntfCq3H/STnYxHGMB5tZbfhV7HE/b45kXfl4qVKdGYLaRj9RMgc0TalZX6BG
	yqmGk6ir8xvU9M=
DKIM-Signature:	v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:from:to:subject:date:message-id:references
	:in-reply-to:content-type:content-transfer-encoding
	:mime-version; s=default; bh=ovFnLgSahcqqXy/0IxWveDZdVZM=; b=lE8
	Lm6wMa40ZMd61ms1wlwsC3b0Yi0Rst2NGGQtmNhEQJHUothzZrbEfdlMLgnUrHpG
	yRebEeF9ElV8o4JEO2VzDtt3OOsH3GUXdMfnwFvMGUb+eZB/DBb+MmvZ6PmdiKFX
	kYbT/7arRnElAK7AWYFuUsMexYAcSSOaOY3RVpF4=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Authentication-Results:	sourceware.org; auth=none
X-Virus-Found:	No
X-Spam-SWARE-Status:	No, score=-1.9 required=5.0 tests=AWL,BAYES_00,MIME_BASE64_BLANKS,RP_MATCHES_RCVD,SPF_HELO_PASS,SPF_PASS autolearn=ham version=3.3.2
X-HELO:	nihxway6out.hub.nih.gov
X-IronPortListener:	Outbound_SMTP
X-IronPort-Anti-Spam-Filtered:	true
X-IronPort-Anti-Spam-Result:	AisFAPA4PFOcKEer/2dsb2JhbABTBoMGgRKDCsBdGYEFFnSCJQEBAQMBEhERSgsCAQgNDQIGIAICAh0TFRABAQQbGodPCKJciiKiKBeBKY0EEjiCbzWBFASOfpBPi0KDMIIr
From:	"Lavrentiev, Anton (NIH/NLM/NCBI) [C]" <lavr AT ncbi DOT nlm DOT nih DOT gov>
To:	"cygwin AT cygwin DOT com" <cygwin AT cygwin DOT com>
Subject:	RE: Tons of cygserver errors
Date:	Wed, 2 Apr 2014 16:26:01 +0000
Message-ID:	<5F8AAC04F9616747BC4CC0E803D5907D0C8AC656@MLBXv04.nih.gov>
References:	<5F8AAC04F9616747BC4CC0E803D5907D0C8AC056 AT MLBXv04 DOT nih DOT gov> <20140402085347 DOT GN2508 AT calimero DOT vinschen DOT de>
In-Reply-To:	<20140402085347.GN2508@calimero.vinschen.de>
MIME-Version:	1.0
X-IsSubscribed:	yes
X-MIME-Autoconverted:	from base64 to 8bit by delorie.com id s32GQObJ020105

> there's really no reason to quote that at all

Maybe, but how would I know that you did not need that?

> It means the pointer to the "signal_arrived" event object is invalid.
> "signal_arrived" is used internally to notify wait functions that a
> POSIX signal arrived for the process and to implement EINTR, for
> instance.  When you're using XSI IPC functions, the signal_arrived
> handle is used in cygserver to make the IPC functions interruptible.
> For that, it creates a local copy of signal_arrived using
> DuplicateHandle
> 
> For some reason the handle given to cygserver is invalid.  Why, I
> have no idea, and your report is missing information, so here we go
> again:

I can’t provide any further information at this point because I do not
understand what and where to look for.  But I have a slight clue that
there is a race in cygserver (and that's not unusual, from my experience).

There is a main process that has sems open / shm attached.  That process
fork()s and exec()s script every now and then.  If the main process
does not spawn any children, there is nothing in the log.  Once it starts
doing that, I see the errors coming in, and in good time correlation with
the spawning schedule.  The spawned processes are very short lived,
merely it's a fork, then exec a shell script with just an exit statement.

I suppose that when cygserver tries to read a handle, the child process
(which by posix rules had inherited the shm and sems, but should have
dropped them altogether at the point of exec()) is already gone, so the
handle is invalid.  Which is why it is the error "6" all way.

How realistic does that sound?

Anton Lavrentiev
Contractor NIH/NLM/NCBI

- Raw text -