This is the mail archive of the
mailing list for the Cygwin project.
Re: "Bad Address" response to many net tools after updating cygwin x86_64 1.7.29
- From: repudi8or repu <repudi8or at gmail dot com>
- To: cygwin at cygwin dot com
- Date: Sun, 20 Apr 2014 21:25:08 +1000
- Subject: Re: "Bad Address" response to many net tools after updating cygwin x86_64 1.7.29
- Authentication-results: sourceware.org; auth=none
- References: <CADKunkFSvokcWUoNxEeqo0yK4dEF9+dkOddgzZGW8oU_5kPzHQ at mail dot gmail dot com>
Thanks Corinna, your link helped me solve the issue. I had also
installed "emisoft anti-malware" as an additional precautionary
measure to scan my environment. This product was for some reason
blocking the cygwin binaries from running and causing the "Bad
address" response every time. I tried excluding the cygwin dir from
being blocked within emsisoft but couldnt get it to work. When I fully
removed the emsisoft product, cygwin was again fully functional.
Much appreciate the assistance.
>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/
On Sat, Apr 19, 2014 at 8:18 PM, repudi8or repu <email@example.com> 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
> 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
> 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
> Any suggestions how i can track down / fix whatever is going wrong here ?
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple