X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-1.7 required=5.0	tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,TW_YG,T_TO_NO_BRKTS_FREEMAIL
X-Spam-Check-By: sourceware.org
MIME-Version: 1.0
In-Reply-To: <4D502B8E.1080306@verizon.net>
References: <4D4EE981 DOT 4060309 AT verizon DOT net>	<20110206191619 DOT GA6839 AT jethro DOT local DOT lan>	<4D4F07FE DOT 4040902 AT verizon DOT net>	<4D4F9389 DOT 4050800 AT dyximaq DOT de>	<4D500DC0 DOT 2020809 AT verizon DOT net>	<4D5015F6 DOT 6030808 AT verizon DOT net>	<AANLkTik5ZxktGVZ0P8H_OaStXFONWn0KzEH7GgRMt7Zm AT mail DOT gmail DOT com>	<4D502B8E DOT 1080306 AT verizon DOT net>
Date: Mon, 7 Feb 2011 18:37:01 +0100
Message-ID: <AANLkTikFeTC6d8LqYCmcQbm0yQcHnV+=kARvPSsjgSBb@mail.gmail.com>
Subject: Re: 1.7.7: PATH in Bash shells
From: marco atzeri <marco DOT atzeri AT gmail DOT com>
To: cygwin AT cygwin DOT com
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT 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

On Mon, Feb 7, 2011 at 6:27 PM, Gerry Reno  wrote:
> On 02/07/2011 12:19 PM, marco atzeri wrote:
>>
>> those scripts are called inside /etc/profile and the execute
>> permission is not needed
>>
>>
>
> Thanks Marco. =A0I had figured that out eventually as well. =A0They are j=
ust
> 'sourced'.
>
> The issue seems to come from the fact that my installation is getting
> "Bad address" on certain file accesses.
>
> And in the 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

that error was related to cmd.exe.
Are you using it ? If so have you tried mintty ?

>
>
> And as I said 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 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
>

Regards
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