From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: 1.7.29-2: Exception from cygwin_gethostname
Date: Thu, 10 Apr 2014 17:49:00 -0000 [thread overview]
Message-ID: <20140410174953.GH2437@calimero.vinschen.de> (raw)
In-Reply-To: <5346D0F7.2040903@acm.org>
[-- Attachment #1: Type: text/plain, Size: 2303 bytes --]
On Apr 10 10:12, 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!
Cool! Thanks for your testing.
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat
[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2014-04-10 17:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-07 18:51 David Rothenberger
2014-04-07 19:09 ` Corinna Vinschen
2014-04-07 19:58 ` Larry Hall (Cygwin)
2014-04-07 20:53 ` David Rothenberger
2014-04-10 9:15 ` Corinna Vinschen
2014-04-10 11:47 ` Ken Brown
2014-04-10 12:22 ` Corinna Vinschen
2014-04-10 16:31 ` David Rothenberger
2014-04-10 17:14 ` David Rothenberger
2014-04-10 17:49 ` Corinna Vinschen [this message]
2014-04-10 20:01 ` David Rothenberger
2014-04-10 20:11 ` David Rothenberger
2014-04-10 21:21 ` David Rothenberger
2014-04-10 23:32 ` David Rothenberger
2014-04-11 2:41 ` Christopher Faylor
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140410174953.GH2437@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).