This is the mail archive of the cygwin-developers@cygwin.com mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: Outstanding issues with current DLL?



----- Original Message -----
From: "Christopher Faylor" <cgf@redhat.com>
To: <cygwin-developers@cygwin.com>
Sent: Friday, 9 March 2001 6:56
Subject: Re: Outstanding issues with current DLL?


> 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.

Good, but can we fix the test. I have found the tests are very good
indicator into the health of my cygwin1.dll build

>
> >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.

The window freezes and I have to use task manager to kill it.
I will try to gdb the exe left in the testsuite....

>
> >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
>

sed and sh give stackdump with no info (well, nothing I can see)

For example :

Exception: STATUS_ACCESS_VIOLATION at eip=00000000
eax=00000000 ebx=00000007 ecx=61084EEC edx=00000000 esi=6108D15C
edi=6108D164
ebp=0241F9F8 esp=0241FE94 program=f:\Cygwin\bin\sed.exe
cs=001B ds=0023 es=0023 fs=003B gs=0000 ss=0023
Stack trace:
Frame     Function  Args
End of stack trace


Regards Trevor







Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]