This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: 1.7.29-2: Exception from cygwin_gethostname
- From: David Rothenberger <daveroth at acm dot org>
- To: cygwin at cygwin dot com
- Date: Thu, 10 Apr 2014 10:12:23 -0700
- Subject: Re: 1.7.29-2: Exception from cygwin_gethostname
- Authentication-results: sourceware.org; auth=none
- 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>
- Reply-to: cygwin at cygwin dot com
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!
--
David Rothenberger ---- daveroth@acm.org
"You tried it just for once, found it alright for kicks,
but now you find out you have a habit that sticks,
you're an orgasm addict,
you're always at it,
and you're an orgasm addict."
-- The Buzzcocks
--
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