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:cc:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; q=dns; s=
	default; b=nvcnbaxY0r6mHxvFBYuAtkMewujvfl++ljX2QXvNSqQPg9fRo5Yr9
	DCG1UchAc7hYyvYcMatnbOwzP2ks3MMaT421ocE0F60zktgA0Bn9GWcYmxC4Ye7c
	ZP4fXrXVUySqOHKPajrQPHv1/b8o88NPGzV6ZktJD18bVTTmbgEZX8=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Date: Thu, 10 Apr 2014 11:15:49 +0200
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Cc: Ken Brown <kbrown AT cornell DOT edu>
Subject: Re: 1.7.29-2: Exception from cygwin_gethostname
Message-ID: <20140410091549.GX2437@calimero.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com, Ken Brown <kbrown AT cornell DOT edu>
References: <5342F343 DOT 6050300 AT acm DOT org> <20140407190942 DOT GU2061 AT calimero DOT vinschen DOT de> <5343035E DOT 4000106 AT cygwin DOT com> <53430FAA DOT 9010409 AT acm DOT org>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;	protocol="application/pgp-signature"; boundary="Qa0ccP92Gc0Ko3P8"
Content-Disposition: inline
In-Reply-To: <53430FAA.9010409@acm.org>
User-Agent: Mutt/1.5.21 (2010-09-15)

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

Hi David,
Hi Ken [in CC],

On Apr  7 13:50, David Rothenberger wrote:
> Larry Hall (Cygwin) wrote:
> > On 4/7/2014 3:09 PM, Corinna Vinschen wrote:
> >> 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.
> >>>
> >>> An strace of ssh shows an exception occuring right after the call to
> >>> cygwin_gethostname is logged.
> >>>
> >>>     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 fir=
st
> >> time I ever saw this and in the above scenario there's no such excepti=
on
> >> expected, so it doesn't get ignored.
> >>
> >> Oh well, it would have been helpful if this had been encountered last
> >> week :(
> >=20
> > Good point.  David, can you go back to last week and see if you can sti=
ll
> > reproduce it? ;-)
>=20
> I wish! There were a few important changes to the system starting last
> Friday and I dearly wish I could go back to before those changes.
>=20
> On Friday, I accidentally installed OpenCandy, a PUP adware "program". I
> spent some time on Saturday cleaning that with a host of free malware
> removals. This removed some registry keys, but I'm pretty sure it was
> all safe. Pretty sure...
>=20
> Also on Saturday I replaced two old HDDs with SSDs. This made my system
> a lot faster, but I haven't seen any problems associated with it aside
> from the OS complaining about not getting a network connection right
> after it boots. I think this is just because it boots so much faster now.
>=20
> I /should/ have tested the snapshots when the call went out. I wished I
> did now, because then I would know if this issue was related to any of
> the problems I had late last week. This is a work machine and we're
> super-busy, so I was hesitant to experiment with snapshots. But I
> learned my lesson; I'll be testing snapshots when Chris or Corinna ask
> for testing from now on, on all my machines.

I have uploaded a new snapshot to http://www.cygwin.com/snapshots/ which
is supposed to workaround this problem by only handling the very
exceptions the exception handler was designed to handle at this point.
Can you please check if this works for you?

Ken, I would also be greatful if you could give this snapshot a try.
You came up with so fascinating testcases.  I tried running emacs-X11 -Q
with this new code and it still works(*), so I'm hopeful the workaround
is ok until we have the ultimate, SEH-based solution (which,
unfortunately, is rather intrusive and so not done in a breeze).

This only affects 64 bit Cygwin so you don't have to test it on
32 bit, in theory.


Corinna


(*) After I wasted two hours on searching for a very weird bug... until
    it occured to me that `fc-cache' might fix it :-P


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

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

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

iQIcBAEBAgAGBQJTRmFFAAoJEPU2Bp2uRE+gNWgP/if23RYYU++pieI+xygS7uTG
LabbT8rMp/FgbdSZ2TiRZmco+6c9X0jbkbjC29nlivPsi65aVwbeYPb6thGreLRK
YnukwlZUYvKlcbgk1H4zwtL4uZSn99Eyj4dZMFHz+/jSVqQeSQCJYIUjled/WR0F
Cf1bV50LdjhmOf8KUUf05GXet1IUozK6MmTsNcNw0LDAp8kwk4cL/+OySQ7bQXV/
6iO1CtYG8cq2KuuxZVrtusklZy1PDEdbRLD6zOt+G5LwFYXBV29zzMo9SVGaE5Ul
OwQbp9x5mp68eEFoDdW9fk+FZ57AYZYk5PXFAztRtP85YuKJAI++2PUzmb0zYdSm
Z6/vroy8AIngCz06ZJ6lRfanN0sePiClQHcf0n8DdGAuyl6x9nvu8JC49HegYUqL
PQJMBZAJASCwsc7EDve38REVHPoJPe8bQRrUfspturxiVVHrBxXEz+Olq7yQ+gBw
b3peRw5ocSSMz5tQRTI9bIaJ4VKP4qWnCjS2tx2NvhF+XHWp9BMeh4IoGoKz9LFd
4LPZMD6yz+9yc/qPBK0TReDfrbVOHjJJdOVjBMs1rNwdbw4+J073+O58q2VQbLmf
PubcIFYHeiGn+FIUUMFNJTKfLmjbMSl5AaYkVtu+qiOuSAyQBW3wjkmeOQJFqfnu
Uj9F5ch+HT1etwXsdYMg
=rrvG
-----END PGP SIGNATURE-----

--Qa0ccP92Gc0Ko3P8--