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=BxBbcjsCuFDbVuzIgrXvAV6RrKc6D0j9mVhEKdeJgxslFQN68pnnG
	3MlplF0v/0zoiFNRAPG28ZqUvNgfr9NYDdZ6UlUMGIKuibicCymDKqzkft6IGqt/
	fFEcJphu7PrmhaxKYTPzXu1m8HXPG09WUbF+m0+A2zD8KgBzg1fjQU=
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=ILml1MCqXVbqWkiIEdhc6haSrPg=; b=ji0QnCEX2CDDwFFvNnUFYqNHyitV
	cSQt+ZUXvQSNVoYT1oAmzcRq5wHVfXXQeFJpUUTM7ovpiZnQZSScg8CzEOe87jgm
	SyBQTj4A+1VI1vXsixC5bJu7lea8PfP25q+Sa5yHz/hrzOvpu8GEEQYsG0N5OUCm
	oIJaeARj53i3jn4=
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=-4.9 required=5.0 tests=AWL,BAYES_00,KHOP_PGP_SIGNED,NO_RELAYS autolearn=ham version=3.3.2
X-HELO: calimero.vinschen.de
Date: Sat, 31 Aug 2013 19:50:07 +0200
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: 20130830, size of shared memory region changed
Message-ID: <20130831175007.GI21571@calimero.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <6EEA8B83-0D67-46CD-8C60-D038BE5E3B97 AT Denis-Excoffier DOT org> <20130831162654 DOT GF21571 AT calimero DOT vinschen DOT de> <27A27F47-9464-451B-ABD6-23970E54CDC8 AT Denis-Excoffier DOT org>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;	protocol="application/pgp-signature"; boundary="QBJnsLb0QyYEYRYK"
Content-Disposition: inline
In-Reply-To: <27A27F47-9464-451B-ABD6-23970E54CDC8@Denis-Excoffier.org>
User-Agent: Mutt/1.5.21 (2010-09-15)

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

On Aug 31 19:39, Denis Excoffier wrote:
> On 2013-08-31 18:26, Corinna Vinschen wrote:
> > On Aug 31 14:00, Denis Excoffier wrote:
> >> Hello,
> >>=20
> >> I'm using Cygwin 32 bits. With the 20130830 snapshot i now get many me=
ssages like:
> >> "      x [main] y z shared_info::initialize: size of shared memory reg=
ion changed from 27984 to 21776"
> >>=20
> >> where x, y and z vary,
> >> - x is typically a small integer (most often 2 or 3, but occurrences w=
ere observed of: 4, 5, 8, 27, even 311)
> >> - y is a program name (tcsh, echo, tr, grep, cut, cat, g++, factor...)
> >> - z is a PID
> >>=20
> >> The name "main" and the numbers 27984 and 21776 seem always present.
> >>=20
> >> It seems that each process initialization would generate a message. Ot=
herwise, all seems OK.
> >=20
> > I can't reproduce this.  The size of the shared_info changed with my
> > tape drive related checkin from 2013-08-26, but your error message
> > points to some older process still running, still using the previous
> > DLL.  Since the shared_info region continues to exist, any newer process
> > using the new DLL will find that its idea of the sizeof shared_info
> > doesn't match what has been noted in shared_info itself.  Nothing else
> > can explain this.
> You're right, and this is only my fault. After logoff/login i was unable
> to reproduce this. In fact, ssh-agent (that i introduced recently in my
> profile, and which i normally kill by 'ssh-agent -k', was not
> actually killed this time since after the replacement of the cygwin1.dll
> launching a new process always fails) is the culprit. I will now always
> logoff/login after installing a new snapshot (and also try to
> double-check my reports more closely in the future...).
>=20
> Sorry for the noise.

No worries, really.  Thanks for letting us know.


Corinna

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

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

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.14 (GNU/Linux)

iQIcBAEBAgAGBQJSIizPAAoJEPU2Bp2uRE+gF9EP/RKSRRKgcO6OKUtFXOFIDfXJ
gSxuZNxtdTyvnaqX3eOlSBuAdzR386YKm2gjuVbor42SbCCewwK9NuVqJDqhbPXH
jdruow7hj4WlWJF1KG4Q+ku2RGIj57TYgksQ+HkSHE4cbEQ5kDeFTXRDJnKdYP3M
D24Kdx/e3Qk2bZ9AMx9Q1zE4b4rEkJc+nmL4LOiGDau4u3xIQfc/eHNOjaTImd3G
d+/+VKSlE3DL9KQXl5C4gE7HoEwj+Wip2lalqaBXp7TWoAuULlpQitByfuxsvRgk
wstL99nz/Lkip38HAkM0DvP8KKUI1rPrX6svMDo4Qgm9d2RqpyQjwbx/uga8PgJ9
J8+ycOpNBFwzPBfLOQYSvUAD9GFwcy9wVilSrLkU4dvzome72dnkxpYBoC5uesQk
AJsNT99nRQY3iqEkGDKPvKfeJgLNBOe580/B6Z6XuBFVVELWQeHJL8uRtgbOJXwl
9QSUe9/lsitAeMmc+ET4gnnyIwD4vLSCJyapgO6uE1lIFFyGpKyGDhw4BfEtzNQ/
eIG8PkWHk4U/nHQS19YrzHbW7qm7r1gCg9H+coPmJPz7s2QizusjgrYw4BMR2i86
mN3EeqgR7txmE55xn7yuVnusiAADPAjTWTkgG+B5tLgq/HxdAoP3fzZNuos86iUN
CtkPMWlzMauBhHSc5GLh
=L+Aq
-----END PGP SIGNATURE-----

--QBJnsLb0QyYEYRYK--