X-Recipient: archive-cygwin AT delorie DOT 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 12:29:32 -0500
Message-ID: <297343D29C14AA4D822142893ABEAEF306570B63@srv1163ex1.flightsafety.com>
In-Reply-To: <20090504171859.GB16424@ednor.casa.cgf.cx>
References: <af075b00904280347s32e89d76ve23b61db6a1c6a8e AT mail DOT gmail DOT com> <20090504082512 DOT GA21324 AT calimero DOT vinschen DOT de> <297343D29C14AA4D822142893ABEAEF306570A42 AT srv1163ex1 DOT flightsafety DOT com> <49FF0586 DOT 3010006 AT sbcglobal DOT net> <20090504151802 DOT GA4286 AT ednor DOT casa DOT cgf DOT cx> <297343D29C14AA4D822142893ABEAEF306570A98 AT srv1163ex1 DOT flightsafety DOT com> <20090504154342 DOT GB4286 AT ednor DOT casa DOT cgf DOT cx> <297343D29C14AA4D822142893ABEAEF306570ABB AT srv1163ex1 DOT flightsafety DOT com> <20090504171859 DOT GB16424 AT ednor DOT casa DOT cgf DOT cx>
From: "Thrall, Bryan" <bryan DOT thrall AT flightsafety DOT com>
To: <cygwin AT cygwin DOT com>
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

Christopher Faylor wrote on Monday, May 04, 2009 12:19 PM:

> On Mon, May 04, 2009 at 10:54:55AM -0500, Thrall, Bryan wrote:
>> Christopher Faylor wrote on Monday, May 04, 2009 10:44 AM:
>>> On Mon, May 04, 2009 at 10:35:46AM -0500, Thrall, Bryan wrote:
>>>> Christopher Faylor wrote on Monday, May 04, 2009 10:18 AM:
>>>>=20
>>>>> 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.
>>>>=20
>>>> Thanks, Greg, for the pointer!
>>>>=20
>>>>> 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.
>>>>=20
>>>> Aren't those the exact symptoms I described?
>>>=20
>>> The "exact symptoms"?  No, in fact it was not.  I was clarifying
what to
>>> look for but I guess I should have said "Please try this from the
>>> windows command line".
>>=20
>> Sorry, I did say:
>>>>>>> - 'cygcheck /bin/ash.exe -v' returns 127
>>>>>>> - it doesn't happen if run from cmd.exe
>=20
> Sorry I missed that.
>=20
>> But I can be more exact:
>=20
>> If I run 'cygcheck /bin/ash.exe -v' from inside cmd.exe, I only get
one copy
>> of the output. I didn't think to check this before, but %ERRORLEVEL%
after
>> running that is -1073741819 (I think that's the normal way to check
return
>> values in cmd.exe?).
>=20
> The windows error code is what I was looking for but again I wasn't
> being very clear.
>=20
> That is a STATUS_ACCESS_VIOLATION, which would be a cygcheck bug.
Wish
> I could duplicate it.

Me too :)

I'll see if I can figure it out, but since this is no longer documented
cygcheck behavior (RE: Corinna's message), I guess it's not a high
priority so it may be a while.
--=20
Bryan Thrall
FlightSafety International
bryan DOT thrall AT flightsafety 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/