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:references
	:mime-version:content-type:in-reply-to; q=dns; s=default; b=tInE
	Y/XiNiORNbvECyae+LhIQDSoT+Ixtyx9ktg9A/hGPvyDp6AD8qAXDs4z0rqLOUUl
	MCdUrUVk+37RHa1umvrd27K53R4aRkETshpQXbQC/SjBCIPBB1HRgJSkFX8Cue4q
	kHM7UmmJfVpovIS3kKDyOwqxqBTCKA3kExE/EJM=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Date: Mon, 7 Apr 2014 21:09:42 +0200
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: 1.7.29-2: Exception from cygwin_gethostname
Message-ID: <20140407190942.GU2061@calimero.vinschen.de>
Mail-Followup-To: cygwin@cygwin.com
References: <5342F343.6050300@acm.org>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;	protocol="application/pgp-signature"; boundary="jcwRHPSxFqmwpRFb"
Content-Disposition: inline
In-Reply-To: <5342F343.6050300@acm.org>
User-Agent: Mutt/1.5.21 (2010-09-15)

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

On Apr  7 11:49, David Rothenberger wrote:
> I'm having a problem doing hostname resolution on one of my Windows
> 7 64 machines after updating cygwin to 1.7.29-2. I first noticed it
> with ssh. I get an error whenever I try to ssh to any machine using
> a hostname; it complains the hostname cannot be resolved.
>=20
> An strace of ssh shows an exception occuring right after the call to
> cygwin_gethostname is logged.
>=20
>    96   58624 [main] ssh 3536 cygwin_gethostname: name daver-pc
> --- Process 3536, exception 000006ba at 000007FEFDD4940D
>   860   59484 [main] ssh 3536 __set_errno: void san::leave():315 setting =
errno 14

Exception 0x6ba is "The RPC server is unavailable".  I have no idea why
this exception is generated at all on your machine.  Usually this is a
first-chance exception only, which can be ignored, but this is the first
time I ever saw this and in the above scenario there's no such exception
expected, so it doesn't get ignored.

Oh well, it would have been helpful if this had been encountered last
week :(


Corinna

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

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

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

iQIcBAEBAgAGBQJTQvf2AAoJEPU2Bp2uRE+gkIgP/i5SqCUxC2PYWyUgOw9YaFof
dst5NoTKVs8xGwH+jJeBzaFo+Fk66MUoDUTJlzzfxWAkGaP9i8LfVG/kWs1RonaW
aFR9F7Gt4gHMuTTZ2z8nck5dhEdYtBJ9MJIqLSj8SvcNAvNda++omNtsYoc+YWBS
TRZZVgoBRA9Gk4WFC18e9csgeH3xdT71j5jv6eJaCIOlymCGQ5Z6al6QDyLkREFG
T80JbKOL9paLXvbanJiXygpPMe9vSNCKj2OandwGvGSpo4gNWmRPO7hpSCoWgBuU
RiPxY0wlo8+BAPkb6JjIlL5JD+ySpkyJrCAs8q78Uj2DrfcTXfO8gMqZ2e5gQfAS
wGnbmGwnPy36iI3v4WMEolI7JdjiRBnvMRoImUM18y0TCbb0aPUqTQoraMFaI33r
oS27TIJA/R2fRwc0HlDigkynfkkl8/veWb3uxbmIwt3E3Py2cphxTGRp4RGNe/6q
e6m+1H0IseAkRaes4unbuqxxyT9z79qoMmgnr22wAtRhn5f2bNab0sNtFCTL+F/h
CbiJeHfl+84PC2cuywmt7TTflomZRUzknYSTTnDdlv3V4CtZSbtW4PbIvgbl8Bs2
vGjtItoVsI/MAe6iAXZEzIgV5dOvReWLrD2j9j5+yZYX2C/3UNOM+WoC5BmMpHsa
eE7sA/XBODy82K9LTAao
=oBMq
-----END PGP SIGNATURE-----

--jcwRHPSxFqmwpRFb--