From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28786 invoked by alias); 7 Feb 2011 20:32:47 -0000 Received: (qmail 28609 invoked by uid 22791); 7 Feb 2011 20:32:46 -0000 X-SWARE-Spam-Status: No, hits=-1.8 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 Received: from mail-fx0-f43.google.com (HELO mail-fx0-f43.google.com) (209.85.161.43) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 07 Feb 2011 20:32:40 +0000 Received: by fxm18 with SMTP id 18so5840926fxm.2 for ; Mon, 07 Feb 2011 12:32:38 -0800 (PST) MIME-Version: 1.0 Received: by 10.223.96.67 with SMTP id g3mr10647745fan.19.1297110758221; Mon, 07 Feb 2011 12:32:38 -0800 (PST) Received: by 10.223.72.12 with HTTP; Mon, 7 Feb 2011 12:32:38 -0800 (PST) In-Reply-To: <4D505111.2090403@verizon.net> References: <4D50379F.8040904@verizon.net> <4D505111.2090403@verizon.net> Date: Mon, 07 Feb 2011 20:32:00 -0000 Message-ID: Subject: Re: 1.7.7: 'Bad address' errors when using Windows 2003 R2 WOW64 From: marco atzeri To: cygwin@cygwin.com Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com X-SW-Source: 2011-02/txt/msg00193.txt.bz2 On Mon, Feb 7, 2011 at 9:07 PM, Gerry Reno wrote: > On 02/07/2011 02:52 PM, marco atzeri wrote: >> On Mon, Feb 7, 2011 at 7:19 PM, Gerry Reno =A0wrote: >> >>> 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 >> >> > > Any why would that be? =A0I quite well know how to report a problem. > I have a different impression. > The previous reported problem was found in Windows 2008. > > This problem is in Windows 2003. > > Different manifestation. =A0Different OS's. =A0A full year and different > Cygwin releases apart. > A lot of thing could be wrong on your machine. Starting with standard problem report will help anyone interested to invest any time in supporting you. Without that effort from you side, it is unlikely that someone will look on= it. > > 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