X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Mon, 4 May 2009 11:18:03 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: [cygcheck] produces repeated output - 6 times! Message-ID: <20090504151802.GA4286@ednor.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <20090504082512 DOT GA21324 AT calimero DOT vinschen DOT de> <297343D29C14AA4D822142893ABEAEF306570A42 AT srv1163ex1 DOT flightsafety DOT com> <49FF0586 DOT 3010006 AT sbcglobal DOT net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <49FF0586.3010006@sbcglobal.net> User-Agent: Mutt/1.5.16 (2007-06-09) 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 Mon, May 04, 2009 at 03:11:02PM +0000, Greg Chicares wrote: >On 2009-05-04 14:44Z, Thrall, Bryan wrote: >> Corinna Vinschen wrote on Monday, May 04, 2009 3:25 AM: >>> On Apr 28 11:47, Julio Costa wrote: >>>> Bug in cygcheck? Or bug in user? :) >>> >>> Bug in user as far as the position of the -v option is concerned. >> >> I can reproduce it; some more details: >> >> - 'cygcheck /bin/ash.exe -v' returns 127 >> - it doesn't happen if run from cmd.exe >> - '/bin/ash.exe -v' from inside bash works just fine >> >> Isn't there a feature of Cygwin where it tries 5 or 6 times to restart >> Windows apps (such as cygcheck) if they fail in a certain way? That >> could explain the repeated output (i.e. cygcheck is trying to do the >> documented 'cygcheck [PROGRAM] -v' thing but there's a bug), but my >> search fu wasn't able to bring up any results. > >Search for 'proc_retry' in the User's Guide. > >Try setting > CYGWIN=proc_retry:1 >to see whether that's what's happening in this case. If it is, then cygcheck would be exiting with a bad status and bash would be causing cygcheck to restart. You wouldn't see the problem from the windows command line. cygcheck itself would not be redoing anything because 1) it isn't a true cygwin program and 2) it isn't starting a process when it displays dll information. cgf -- 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/