Outstanding issues with current DLL?

Christopher Faylor cgf@redhat.com
Thu Mar 8 13:26:00 GMT 2001

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?


More information about the Cygwin-developers mailing list