X-Recipient: archive-cygwin@delorie.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: <4D505111.2090403@verizon.net> Date: Mon, 07 Feb 2011 15:07:45 -0500 From: Gerry Reno 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@cygwin.com Subject: Re: 1.7.7: 'Bad address' errors when using Windows 2003 R2 WOW64 References: <4D50379F.8040904@verizon.net> In-reply-to: Content-type: text/plain; charset=ISO-8859-1 Content-transfer-encoding: 7bit X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com On 02/07/2011 02:52 PM, marco atzeri wrote: > 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. I 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: >> >> http://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: http://cygwin.com/problems.html >> > Marco > > Any why would that be? I quite well know how to report a problem. The previous reported problem was found in Windows 2008. This problem is in Windows 2003. Different manifestation. Different OS's. A full year and different Cygwin releases apart. Regards, Gerry -- 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