Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com Date: Thu, 8 Mar 2001 16:26:47 -0500 From: Christopher Faylor To: cygwin-developers AT cygwin DOT com Subject: Re: Outstanding issues with current DLL? Message-ID: <20010308162647.A4646@redhat.com> Reply-To: cygwin-developers AT cygwin DOT com Mail-Followup-To: cygwin-developers AT cygwin DOT com References: <20010307200848 DOT A32670 AT redhat DOT com> <20010307213711 DOT E32721 AT redhat DOT com> <005801c0a811$018d6d10$0200a8c0 AT voyager> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.11i In-Reply-To: <005801c0a811$018d6d10$0200a8c0@voyager>; from trevorforbes@ozemail.com.au on Fri, Mar 09, 2001 at 06:17:32AM +0930 On Fri, Mar 09, 2001 at 06:17:32AM +0930, Trevor Forbes wrote: >Anyway, did you do a make check on winsup... >I did and it is failing in two areas > > X_OK is defined as a constant unsigned in file.h cygwin_S_IEXEC.cc >and /src/cygwin/src/winsup/testsuite/winsup.api/ltp/access01.c:147: >gives the error: initializer element is not constant > >file -- access01.c >.. >static struct test_case_t { > char *file; > int mode; > char *string; > int experrno; >} Test_cases[] = { > { Fname, F_OK, "F_OK", 0 }, > { Fname, X_OK, "X_OK", 0 }, <------ access01.c:147 > { Fname, W_OK, "W_OK", 0 }, > { Fname, R_OK, "R_OK", 0 }, >}; > >I think X_OK has to be an int in your "interesting" changes Actually, to circumvent this, it has to be a constant. That would blow my change out of the water. >and the second area it is failing is >running /src/cygwin/obj/i686-pc-cygwin/winsup/testsuite/../cygwin/cygrun >./sigchld.exe > ./sigchld.log >it just locks up and cannot be stopped Can you attach a gdb to this? I've had hardware errors for a few weeks now that are causing problems when I try to "do too much" on my Windows system so I can't easily check this myself. >Other than the test failures I was having a lot of trouble just >building the dll due to random failures. What kind of random failures are you seeing? Hanging? SIGSEGVs? cgf