This is the mail archive of the cygwin mailing list for the Cygwin project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
On Apr 19 20:18, repudi8or repu wrote: > I decided to update my cygwin x86_64 environment a few days back out > of concern about the openssh heartbleed bug. > > Since that time most of my network tools no longer work as expected, > reporting "Bad address" as the failure reason > > Here are some samples:- > > rep@WinServer:~$ ping 192.168.1.1 > -bash: /cygdrive/c/Windows/system32/ping: Bad address > rep@WinServer:~$ which ping > /cygdrive/c/Windows/system32/ping > rep@WinServer:~$ file /cygdrive/c/Windows/system32/ping > /cygdrive/c/Windows/system32/ping: PE32+ executable (console) x86-64, > for MS Windows > > rep@WinServer:~$ netstat -na > -bash: /cygdrive/c/Windows/system32/netstat: Bad address > rep@WinServer:~$ which netstat > /cygdrive/c/Windows/system32/netstat > rep@WinServer:~$ file /cygdrive/c/Windows/system32/netstat > /cygdrive/c/Windows/system32/netstat: PE32+ executable (console) > x86-64, for MS Windows > > rep@WinServer:~$ wget www.google.com > --2014-04-19 20:03:25-- http://www.google.com/ > Resolving www.google.com (www.google.com)... failed: Bad address. > wget: unable to resolve host address âwww.google.comâ > > and so on and so forth. Did some googling of the error, nothing recent > that seems immediately obvious. The same tools work ok from windows > command prompt. > > rep@WinServer:~$ uname -a > CYGWIN_NT-6.1 WinServer 1.7.29(0.272/5/3) 2014-04-07 13:46 x86_64 Cygwin All your examples work fine for me using the same DLL: $ uname -a CYGWIN_NT-6.3 vmbert8164 1.7.29(0.272/5/3) 2014-04-07 13:46 x86_64 Cygwin > Any suggestions how i can track down / fix whatever is going wrong here ? That looks certainly like a local problem, maybe a BLODA: http://cygwin.com/faq/faq.html#faq.using.bloda. Did you update more than just Cygwin, by any chance? Do the Windows event logs show something? Alternatively, maybe something broke during update. Reinstalling Cygwin might fix this. Or rebasing. You could also try if a recent snapshot of the Cygwin DLL helps since there was a change in exception handling: http://cygwin.com/snapshots/ Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat
Attachment:
pgpPGTI1BNQFP.pgp
Description: PGP signature
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |