Mail Archives: cygwin/1999/03/29/15:21:02
N8TM AT aol DOT com wrote:
> In a message dated 3/26/99 6:35:26 AM Pacific Standard Time,
> Charles DOT Gauthier AT iit DOT nrc DOT ca writes:
>
> > all execution tests fail under cygwin
> This has been my experience under NT (cygnus installed on //d), but not under
> W95 (//d is a zip drive). Maybe you're right about the drive name thing; that
> was true of all software running under cygwin snapshots for a while, but not
> recently.
>
So far, I only found that the expect interpreter has the pathname problem. All
other cygwin tools appear ok. //<drive letter>/ did not work either. It had to be
a relative path, or start with a dirver letter and colon.
>
> >The dejagnu framework appears to be very unstable under cygwin. During
> execute
> >tests, I appear to get SEGV signals at random. I just don't trust the test
> >results; every test passes until a SEGV stops the testing of a given suite.
>
> Several of the tests generate intentional access violations, and the cygwin
> expect doesn't recover. I'd like to see a solution.
>
In my experience, successive runs of the same tests crash at different points,
hence my statement that I get SEGV signals at random.
>
> --
> Want to unsubscribe from this list?
> Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com
--
Charles-Antoine Gauthier
Research Officer
Software Engineering Group
Institute for Information Technology
National Research Council of Canada
Ottawa, ON, Canada
K1A 0R6
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com
- Raw text -