DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:mime-version:in-reply-to:references:date
	:message-id:subject:from:to:content-type
	:content-transfer-encoding; q=dns; s=default; b=aS4Sy11qU3fCQmXc
	8LWR8J7fQq3/fWHKLUe9wUxPX1PGkZs3/JoMOFbfCvaz4e7FpuaD2mcnZUnZN0ci
	fCXm02bTqxcZxwqkyVroKUg81K0iidA9va8v3Pd5bgXITzBvcpcJ914fciBjvLyC
	WP9xXDFMcNsSSROksIX7HHWWgv8=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
MIME-Version: 1.0
In-Reply-To: <CADKunkFSvokcWUoNxEeqo0yK4dEF9+dkOddgzZGW8oU_5kPzHQ@mail.gmail.com>
References: <CADKunkFSvokcWUoNxEeqo0yK4dEF9+dkOddgzZGW8oU_5kPzHQ AT mail DOT gmail DOT com>
Date: Sun, 20 Apr 2014 21:25:08 +1000
Message-ID: <CADKunkEq4rLgiG17nj60RQ4T5Rf9+6P2E2k3MWu7RfgZ4CG6+g@mail.gmail.com>
Subject: 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
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

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.

Regards Rep

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

On Sat, Apr 19, 2014 at 8:18 PM, repudi8or repu <repudi8or AT gmail DOT 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 AT WinServer:~$ ping 192.168.1.1
> -bash: /cygdrive/c/Windows/system32/ping: Bad address
> rep AT WinServer:~$ which ping
> /cygdrive/c/Windows/system32/ping
> rep AT WinServer:~$ file /cygdrive/c/Windows/system32/ping
> /cygdrive/c/Windows/system32/ping: PE32+ executable (console) x86-64,
> for MS Windows
>
> rep AT WinServer:~$ netstat -na
> -bash: /cygdrive/c/Windows/system32/netstat: Bad address
> rep AT WinServer:~$ which netstat
> /cygdrive/c/Windows/system32/netstat
> rep AT WinServer:~$ file /cygdrive/c/Windows/system32/netstat
> /cygdrive/c/Windows/system32/netstat: PE32+ executable (console)
> x86-64, for MS Windows
>
> rep AT 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 AT 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 ?
>
> Thanks

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