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:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; q=dns; s=
	default; b=cBt9nLcMn9qM8uT8Q0HBFIiYBGxtzkatQt9D5l+O+bZlqLb8zgm9D
	iT6GBuXh9Lvv/O/o/ZhXCCB+VROZNgLtuc4kLkgfMFkOMyZrJZS0XLHIsNQGBXO1
	NfRi7JzJSgzgy86a6XbUW28ei4lnMPLxaO6SNAOT8BXlEIOmaNT29w=
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:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; s=default;
	bh=CftvtVuFl/zndYoEJMSs9KY3IQc=; b=M32ULAtvwFvPJZtGwMi1KpVResYR
	GyDuZs0fgBlZNX9EjkFTkv2fT/nLvw8bxt8CoQVHjsW4fJqSV4H06/IQFZqAfAFC
	te9NcofdbLG65vQ8bYx8Zg2B7mwwpIt8ludS3GbmOeXRz0P4ANJLfmh3dOTnjRsv
	F47qSU35BBR3zMU=
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=-5.9 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.3.2
X-HELO:	calimero.vinschen.de
Date:	Thu, 3 Apr 2014 10:27:58 +0200
From:	Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: Tons of cygserver errors
Message-ID:	<20140403082758.GV2508@calimero.vinschen.de>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<5F8AAC04F9616747BC4CC0E803D5907D0C8AC056 AT MLBXv04 DOT nih DOT gov> <20140402085347 DOT GN2508 AT calimero DOT vinschen DOT de> <5F8AAC04F9616747BC4CC0E803D5907D0C8AC656 AT MLBXv04 DOT nih DOT gov>
MIME-Version:	1.0
In-Reply-To:	<5F8AAC04F9616747BC4CC0E803D5907D0C8AC656@MLBXv04.nih.gov>
User-Agent:	Mutt/1.5.21 (2010-09-15)

--XMHqbYJb993HXwLR
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Apr  2 16:26, Lavrentiev, Anton (NIH/NLM/NCBI) [C] wrote:
> > there's really no reason to quote that at all
>=20
> Maybe, but how would I know that you did not need that?

That's why I said "for the records" :)

> > 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
> >=20
> > 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:
>=20
> I can=E2=80=99t provide any further information at this point because I d=
o 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).
>=20
> 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.
>=20
> 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.
>=20
> How realistic does that sound?

Still, you're missing the cygcheck log, and a simple testcase would
be helpful.


Corinna

--=20
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

--XMHqbYJb993HXwLR
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBAgAGBQJTPRuOAAoJEPU2Bp2uRE+gTH0QAIrXM+Oa9EM7Ufq3t8iDJvx4
YDn5DuyuRm1ma3omaJp+xs5WT0KdSyFckvEv0dx1V0bS6HKLmr5yQMyXIP9226kK
pxoUgHOa8tA80PhQ+fcqXUMu9mNPO2nfhGPehrT9LQF9STiCbjZkrmVv+mptA3Po
WnGI9iEKTToUtkwNQFCSJVC17tfiVWdStmefwCRqlr+5z0WVwVWPWYvDVfYoSv3e
YhEkNTzDhfR/add5+2QoHMjWcayJwDkPXmxpgmvzvwEXHZ2b4eMkYCMCVbQ8f00u
OTyR4ex75pDLFlxyCj1oaUZTeoVNn6BEXRNHYIjyd7yBoqKhtwDwJxCqqFjawA8L
N6Swx7x90+33x6Sw2b51q35oWiy4/cLT15dsQc9/71CSbATY+n52d+SipYm7d79I
X+HyXGXPgGVIOsXXTJdKmoCovSZVI6ZjsD/TDnhMjVmD4FLYdeTVXfz4XJXwnfE4
G4OKG35evE0gaRhq7qAaf+jpMYTPyCK7dNI1hF+0A5wlBW0JsGsgQpi6ZP6PM0xL
7TP5lSSBSCUpPEJEmSQhBMLw+9EzTmwsIHI5JgC9cGVxk2qgiEcGYJ9KZn3k7+lO
qBl4oVix0p2lmAI2c38e98iFg8KkgdfKSdlY23DMVNKPCLmMhw+c7//v1orNNTef
/EYRzThzwx3AeZbQVOs0
=QJaD
-----END PGP SIGNATURE-----

--XMHqbYJb993HXwLR--

- Raw text -