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 23:03:14 -0400 From: Christopher Faylor To: cygwin-developers AT cygwin DOT com Subject: Re: Many pthread failures in the test suite, one setgroup failure Message-ID: <20020929030314.GA13620@redhat.com> Reply-To: cygwin-developers AT cygwin DOT com Mail-Followup-To: cygwin-developers AT cygwin DOT com References: <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> <20020929020609 DOT GB11549 AT redhat DOT com> <1033265603 DOT 4374 DOT 95 DOT camel AT lifelesswks> <20020929022338 DOT GA12659 AT redhat DOT com> <1033267203 DOT 4374 DOT 100 DOT camel AT lifelesswks> <20020929024420 DOT GA13416 AT redhat DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020929024420.GA13416@redhat.com> User-Agent: Mutt/1.4i On Sat, Sep 28, 2002 at 10:44:20PM -0400, Christopher Faylor wrote: >On Sun, Sep 29, 2002 at 12:40:02PM +1000, Robert Collins wrote: >>On Sun, 2002-09-29 at 12:23, Christopher Faylor wrote: >>> On Sun, Sep 29, 2002 at 12:13:23PM +1000, Robert Collins wrote: >>> >On Sun, 2002-09-29 at 12:06, Christopher Faylor wrote: >>> >> How about if I actually just give you a debugging version of the DLL? >>> >> Then you can duplicate the problem for yourself, presumably. >>> > >>> >Sure. >>> >>> ftp://sourceware.org/pub/cygwin/tmp/new-cygwin1.dll.bz2 >>> md5sum: 1f5f2a5675ee8cd54604a09da96c211e >> >>Ha!. Well pthread_cond6 passes using this dll. > >You sure you're actually using this DLL? As new-cygwin1.dll? That's what >the test suite code needs. And, it needs to be in the winsup/cygwin directory. It couldn't hurt to have this as your /bin/cygwin1.dll, either. I think I'm still seeing strange problems when the system cygwin1.dll is not the same as the new-cygwin1.dll. cgf