MIME-Version: 1.0
In-Reply-To: <4D50379F.8040904@verizon.net>
References: <4D50379F.8040904@verizon.net>
Date: Mon, 7 Feb 2011 20:52:18 +0100
Message-ID: <AANLkTin_HxUNot+EvZz6+dc=AmA+_qt8gpWupwYH1b=K@mail.gmail.com>
Subject: Re: 1.7.7: 'Bad address' errors when using Windows 2003 R2 WOW64
From: marco atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

On Mon, Feb 7, 2011 at 7:19 PM, Gerry Reno  wrote:
> I'm retitling this issue to reflect the proper topic.
>
>
> My Cygwin installation on Windows 2003 R2 WOW64 is getting "Bad address"
> on certain file accesses. =A0I observed this when running a bash login
> shell where when /etc/profile is being run errors of the type: 'Bad
> address' are seen when trying to run the scripts in /etc/profile.d/
> directory.
>
> And in this thread it appears to be related to running on 64 bit
> hardware even when using 32 bit mode:
>
> =A0 =A0http://www.cygwin.com/ml/cygwin/2010-01/msg00933.html
>
>
> And as I said in my previous postings under "1.7.7: PATH in Bash shells"
> we are running Windows 2003 DATACENTER R2 WOW64 as shown in the cygcheck
> output I attached to a previous posting.
>
> So it appears that if this "Bad address" problem was fixed from the last
> problem report that apparently there are still some places where it
> occurs and I'd like to find out from the Cygwin developers what we can
> do to work around the issue or if they could fix the problem.
>
>
> Regards,
> Gerry
>
>
> --

Gerry
You missed this point

> Problem reports: =A0 =A0 =A0 http://cygwin.com/problems.html

Marco

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