Mailing-List: contact cygwin-developers-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT cygwin DOT com Delivered-To: mailing list cygwin-developers AT cygwin DOT com Date: Sat, 28 Sep 2002 22:06:09 -0400 From: Christopher Faylor To: Robert Collins Cc: cygwin-developers AT cygwin DOT com Subject: Re: Many pthread failures in the test suite, one setgroup failure Message-ID: <20020929020609.GB11549@redhat.com> Reply-To: cygwin-developers AT cygwin DOT com Mail-Followup-To: Robert Collins , cygwin-developers AT cygwin DOT com References: <20020925141653 DOT GA6134 AT redhat DOT com> <1033139976 DOT 22908 DOT 333 DOT camel AT lifelesswks> <163544913434 DOT 20020927192540 AT logos-m DOT ru> <1033140780 DOT 9593 DOT 0 DOT camel AT lifelesswks> <44642850720 DOT 20020928223759 AT logos-m DOT ru> <1033254454 DOT 4375 DOT 48 DOT camel AT lifelesswks> <20020929000215 DOT GB10872 AT redhat DOT com> <1033264646 DOT 4375 DOT 78 DOT camel AT lifelesswks> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1033264646.4375.78.camel@lifelesswks> User-Agent: Mutt/1.4i On Sun, Sep 29, 2002 at 11:57:26AM +1000, Robert Collins wrote: >On Sun, 2002-09-29 at 10:02, Christopher Faylor wrote: > >> Already did that. It brings the pthread test suite failures down to >> 1 for pthread-condvar6. assertion output is below. > >> Assertion failed: (pthread_cond_timedwait(&cvthing.notbusy, &cvthing.lock, &abstime) == 0), file /cygnus/src/uberbaum/winsup/testsuite/winsup.api/pthread/condvar6.c, line 97 >> Assertion failed: (pthread_cond_timedwait(&cvthing.notbusy, &cvthing.lock, &abstime) == 0), file /cygnus/src/uberbaum/winsup/testsuite/winsup.api/pthread/condvar6.c, line 97 > >Can you get me the actual value returned by timedwait? It will help me >tracing the behaviour. How about if I actually just give you a debugging version of the DLL? Then you can duplicate the problem for yourself, presumably. cgf