X-Recipient:	archive-cygwin AT delorie DOT com
DomainKey-Signature:	a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; q=dns; s=
	default; b=Qtf7qzhag7SdMQxjQ6AJ6isbcLtHGmI64d0B04C9Yhu/PfxaIkQOp
	ndzZD7BE3T/jZSSN2/NSeLS722OLH3+P+LUha9Ury8Jjjci3HTgUTHYPe9IBV9op
	TvY25XNeRCwDJ3JhnJrRPNeBR2XCC3tiLJAzU4wV/XtdLlW6ybXtuc=
DKIM-Signature:	v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; s=default;
	bh=JdoZgYQzT2UKMO9BVJjuN+McrBU=; b=eyh9R97FZksI7HECA/Xfdflg/M0e
	57199hgdiA3hVnQO89tkRZnHLGrL2T3As8NRHTYHRorC2EpnYq+v62S6/1YnPWAB
	HJMhhW+vYFSYHBO+Tyhnf3/mxRq/a1zxTbRY3o2C2Scsy4K5AuVG+9X3VIvsjWU8
	XvjOLBj4yRsNfS4=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Authentication-Results:	sourceware.org; auth=none
X-Virus-Found:	No
X-Spam-SWARE-Status:	No, score=-5.9 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.3.2
X-HELO:	calimero.vinschen.de
Date:	Sat, 19 Apr 2014 13:32:59 +0200
From:	Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: "Bad Address" response to many net tools after updating cygwin x86_64 1.7.29
Message-ID:	<20140419113259.GH16638@calimero.vinschen.de>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<CADKunkFSvokcWUoNxEeqo0yK4dEF9+dkOddgzZGW8oU_5kPzHQ AT mail DOT gmail DOT com>
MIME-Version:	1.0
In-Reply-To:	<CADKunkFSvokcWUoNxEeqo0yK4dEF9+dkOddgzZGW8oU_5kPzHQ@mail.gmail.com>
User-Agent:	Mutt/1.5.21 (2010-09-15)

--2FkSFaIQeDFoAt0B
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

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.
>=20
> Since that time most of my network tools no longer work as expected,
> reporting "Bad address" as the failure reason
>=20
> Here are some samples:-
>=20
> 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
>=20
> 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
>=20
> 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 =E2=80=98www.google.com=E2=80=99
>=20
> 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.
>=20
> 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

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

--=20
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

--2FkSFaIQeDFoAt0B
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBAgAGBQJTUl7rAAoJEPU2Bp2uRE+gGAkQAKF1Jy6uEOTwIZ8fZqOCPaBN
/9iGHiu14WLBQPLlO5Gi/4HoCHdyqNYl+9HJhWiKUr6mduzNBxsoLVe16ax7H9wi
jwU3Pb/ryM+nnd5ch5w4NA4uaZ4c/NU4qsjFkh0bUbUurIdC95Lmti1UQNQcHMdw
PiulYPgZv3u44S3i/M/UTDtD7Vzw0DIikVAkAkR4zbsVLTdH5B92odHQc4CYBXcZ
AGpx0KnvSmQnuRTghlGHnzVZlTHnw99qvqSb16CCG4If4P78btKZQeCV5KLvcxQM
tEw82hvV2kMFXl5vdcfKYCA6SShWxxP/n348mgJMnZTZuXBKb+CvKBU0/7fY1ZFA
d44kgguavVtat2ajZIllqMHa6oxUzZyshfg0eeV7u+kKl+CZKW/xrn0gego4zYaQ
bEO6bMBtSaRVm4+J5j6KLpIUJgj9V+QG81mVDYYXf9IZpPlWNtDd7VplaYn5r4en
4WXO4lShXn8Ky8/OFpeXGuKdlX5w9iyPnSyvFNjke+CficECXyDoHcjsXa07NiIx
2o6u2ItIL832L8++D7gw9NZtRqL4X+5KhdkljqpSNBkXnzif/AVuTx22/LxBtNdc
Q5Tz4vZdIr/5JkhyzmexvYs1aYKyoegGxSg7BFvCQGrCXDKQxAqc5hUmVhlbchgQ
RgbUVMu0JdJKZ+inuDU9
=z6Bc
-----END PGP SIGNATURE-----

--2FkSFaIQeDFoAt0B--

- Raw text -