| delorie.com/archives/browse.cgi | search |
| X-Recipient: | archive-cygwin AT delorie DOT com |
| X-SWARE-Spam-Status: | No, hits=-48.4 required=5.0 tests=AWL,BAYES_00,BOTNET,RCVD_IN_DNSWL_NONE,RFC_ABUSE_POST,TW_YG,T_RP_MATCHES_RCVD |
| X-Spam-Check-By: | sourceware.org |
| Message-id: | <4D502F41.40901@verizon.net> |
| Date: | Mon, 07 Feb 2011 12:43:29 -0500 |
| From: | Gerry Reno <greno AT verizon DOT net> |
| User-Agent: | Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.9) Gecko/20100430 Fedora/3.0.4-2.fc11 Thunderbird/3.0.4 |
| MIME-version: | 1.0 |
| To: | cygwin AT cygwin DOT com |
| Subject: | Re: 1.7.7: PATH in Bash shells |
| 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> <AANLkTikFeTC6d8LqYCmcQbm0yQcHnV+=kARvPSsjgSBb AT mail DOT gmail DOT com> |
| In-reply-to: | <AANLkTikFeTC6d8LqYCmcQbm0yQcHnV+=kARvPSsjgSBb@mail.gmail.com> |
| X-IsSubscribed: | yes |
| 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 |
On 02/07/2011 12:37 PM, marco atzeri wrote: > 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. I had figured that out eventually as well. They are just >> '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: >> >> http://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 ? > I have no idea what code might be using cmd.exe in Cygwin under the covers. No, I'm not using mintty. Don't see how that would make any difference. It's just a terminal. > >> >> 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 > > > -- 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
| webmaster | delorie software privacy |
| Copyright © 2019 by DJ Delorie | Updated Jul 2019 |