X-Recipient: archive-cygwin@delorie.com X-SWARE-Spam-Status: No, hits=-2.1 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: [cygcheck] produces repeated output - 6 times! Date: Mon, 4 May 2009 10:35:46 -0500 Message-ID: <297343D29C14AA4D822142893ABEAEF306570A98@srv1163ex1.flightsafety.com> In-Reply-To: <20090504151802.GA4286@ednor.casa.cgf.cx> References: <20090504082512.GA21324@calimero.vinschen.de> <297343D29C14AA4D822142893ABEAEF306570A42@srv1163ex1.flightsafety.com> <49FF0586.3010006@sbcglobal.net> <20090504151802.GA4286@ednor.casa.cgf.cx> From: "Thrall, Bryan" To: X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 Christopher Faylor wrote on Monday, May 04, 2009 10:18 AM: > 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? :) >>>>=20 >>>> Bug in user as far as the position of the -v option is concerned. >>>=20 >>> I can reproduce it; some more details: >>>=20 >>> - '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 >>>=20 >>> 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. >>=20 >> Search for 'proc_retry' in the User's Guide. >>=20 >> Try setting >> CYGWIN=3Dproc_retry:1 >> to see whether that's what's happening in this case. Thanks, Greg, for the pointer! > 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. Aren't those the exact symptoms I described? > 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. Unfortunately, unless I'm doing something wrong, it isn't due to proc_retry: thrall@pc1163-8413-xp ~ $ echo $CYGWIN thrall@pc1163-8413-xp ~ $ cygcheck /bin/ash.exe -v C:\cygwin_1.7\bin\ash.exe C:\cygwin_1.7\bin\cygwin1.dll C:\WINDOWS\system32\ADVAPI32.DLL C:\WINDOWS\system32\ntdll.dll C:\WINDOWS\system32\KERNEL32.dll C:\WINDOWS\system32\RPCRT4.dll <5 more copies of the DLL info> thrall@pc1163-8413-xp ~ $ export CYGWIN=3Dproc_retry:1 thrall@pc1163-8413-xp ~ $ cygcheck /bin/ash.exe -v C:\cygwin_1.7\bin\ash.exe C:\cygwin_1.7\bin\cygwin1.dll C:\WINDOWS\system32\ADVAPI32.DLL C:\WINDOWS\system32\ntdll.dll C:\WINDOWS\system32\KERNEL32.dll C:\WINDOWS\system32\RPCRT4.dll <5 more copies of the DLL info> Oh well, at least I learned something :) --=20 Bryan Thrall FlightSafety International bryan.thrall@flightsafety.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/