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
	:reply-to; q=dns; s=default; b=XfaKbB1Eu8dYq7yL0OHvE30X+5287fnuN
	2RLWGc921j2ubI6dx4cMf0h2jcwhE583+f9OVgRXWpmobQJc9sjstRbAI19QFBIa
	ygylXBODcyWLfNzMQqJBdQZQ+0qzeEZaJ1WIUJzkO0tmsQDMgEmF9msJD4w1gQ1e
	LWBE5utAAM=
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
	:reply-to; s=default; bh=j6Ny2XuVDuH7umtTJD0TMIqsp6k=; b=fmiGp+7
	6uh3zr4DLTs1M/83tiuumel70cawqAulvfnzRWOisSsDyzY0mZrIkDyjKM4M6oy2
	NyjaDpMhxTr8ilIJo43cJONNwGlxzhSXaQfPK4MN3AnwQyLBwgvuldPKUhK77Hto
	cfbhdtABnc3i/+iv3+Ko5xHsV4Yruweabgyk=
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=-0.3 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,SPF_SOFTFAIL autolearn=no version=3.3.2
X-HELO:	qmta03.emeryville.ca.mail.comcast.net
Message-ID:	<5346FA81.20803@acm.org>
Date:	Thu, 10 Apr 2014 13:09:37 -0700
From:	David Rothenberger <daveroth AT acm DOT org>
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> <5346C6C0 DOT 104 AT acm DOT org> <5346D0F7 DOT 2040903 AT acm DOT org> <5346F80C DOT 9000301 AT acm DOT org>
In-Reply-To:	<5346F80C.9000301@acm.org>
X-IsSubscribed:	yes
Reply-To:	cygwin AT cygwin DOT com

David Rothenberger wrote:
> David Rothenberger wrote:
>> David Rothenberger wrote:
>>> 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 :(
>>>>
>>>> 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?
>>>
>>> Thanks, Corinna. That solves my problem.
>>>
>>> A co-worker had a slightly different problem with 1.7.29-2. I'll test
>>> the snapshot on his machine as soon as he's available today and report
>>> back.
>>
>> The snapshot fixes the problem on my co-worker's machine as well. Thanks
>> again!
> 
> Looks like I spoke too soon. It fixed my simple test case of running
> ssh, but I still get the exception when I try to run "git push", where
> git spawns ssh. The exception is exactly the same as before (same
> address too).

Hmm... And this time rolling back to 1.7.28 did not fix my problem. And
my co-worker is not having any problem with the snapshot.

My crystal ball is telling me a Windows re-install is in my future. :(

-- 
David Rothenberger  ----  daveroth AT acm DOT org

A light wife doth make a heavy husband.
                -- Wm. Shakespeare, "The Merchant of Venice"

--
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

- Raw text -