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:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	 q=dns; s=default; b=Tu+njApl3KZ5Az7/eEeMyhxxLp6jNibuwj1CHlid6UH
	jyxsEtLlhhL5A9DBxmhzITkZ+0WVxlfbnYVq3NKSbD2NMv6vQfU06+Wum0GPJEbg
	9mcqy10kkQHzwnG50PmVMVQqLx09/6UXtSMNBKRxNZbFLIpTHA/+/k3KFwXBp+Yc
	=
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:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	 s=default; bh=ePSIv/WEKM5EqGxzobBXW7En4rA=; b=DLcexQlFVX/QFjUoH
	NB/3EedKHBtbhm2YpVeLs9APBj3eUkIiuQvuB3vWeVXEDpOFmfHa5iIgd6nPJK1m
	BMkXNd1vKGUInCFsEEaCBYmo8CWTggBGcefeAoZei1XQgv/8s4cuJkfybF8LXTXq
	KmFR0fsb4gOG4zrmfHWuEahMuw=
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=-2.0 required=5.0 tests=AWL,BAYES_00,RP_MATCHES_RCVD,SPF_PASS autolearn=ham version=3.3.2
X-HELO: limerock01.mail.cornell.edu
X-CornellRouted: This message has been Routed already.
Message-ID: <534684B7.1040407@cornell.edu>
Date: Thu, 10 Apr 2014 07:47:03 -0400
From: Ken Brown <kbrown AT cornell DOT edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: 1.7.29-2: Exception from cygwin_gethostname
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> <20140410091549 DOT GX2437 AT calimero DOT vinschen DOT de>
In-Reply-To: <20140410091549.GX2437@calimero.vinschen.de>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes

On 4/10/2014 5:15 AM, Corinna Vinschen wrote:
> 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 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 :(
>>>
>>> Good point.  David, can you go back to last week and see if you can still
>>> reproduce it? ;-)
>>
>> 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.
>>
>> 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...
>>
>> 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.
>>
>> 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.

It works fine for me so far (tested 64 bit only).  I ran all the 
previous testcases with no problems.

Sorry about the fc-cache problem.  Yaakov, any further thoughts on this?

Ken

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple