X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Fri, 8 Aug 2008 01:38:52 -0500 (CDT) From: tmcd AT panix DOT com To: cygwin AT cygwin DOT com Subject: Re: bash builtin "test" kills bash on Win 2003 Server R2 x64 (some hardware) In-Reply-To: <489B470D.3000004@cygwin.com> Message-ID: References: <2AF7DD0CE564C24EBACDABFAE55CC642042863D3 AT srv DOT odcnet DOT local> <489B470D DOT 3000004 AT cygwin DOT com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , 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 Thu, 7 Aug 2008, Larry Hall (Cygwin) wrote: > But leaving that aside for the moment, perhaps you have a a > corrupted '/bin/[.exe'. Yes, it's just a WAG that really shouldn't > be an issue but given your unique environment, maybe it's worth > checking. I don't have the original note handy, but I thought it was of the form if [ ... ] As the subject line noted, [ is a shell builtin in bash (and I think even in sh of recent decades), so I don't see how it could be affected by corruption of anything other than /bin/bash.exe. If the original code was if /bin/test ... or if /bin/[ ... ] then it would be likelier. -- Tim McDaniel; Reply-To: tmcd AT panix DOT com -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/