Re: Re: screen echos from cygwin1-20010225.dll

Re: Re: screen echos from cygwin1-20010225.dll

[tprinceusa]

I have the standard cygwin up to date as done by the standard installer, but with the snapshot cygwin1.dll added. expect 20010117 was most recently installed. The first big batch of messages starts immediately upon beginning the gcc testsuite, as my posted screen echo shows.  I have not watched that make check closely recently; I believe it has already completed some instances of expect before this happensl.  

I have not attempted to build cygwin1.dll myself for many months, but I will try that if it will help.

IIRC, a similar thing happened (diagnostic messages, maybe not the same ones) with a pre-1.1.7 snapshot of the .dll but they were cleaned up in the released .dll.  The 1.1.8 .dll, of course, will not run this sequence.

Egor Duda <cygwin@cygwin.com> wrote:
> Hi!

Thursday, 08 March, 2001 Tim Prince tprince@computer.org wrote:

TP> I don't see these as build errors; maybe I'm missing something.  expect
TP> runs the same with the 1.1.7 cygwin1.dll and with the post-1.1.8
TP> snapshots, except for these additional messages.  The results from gcc
TP> and g77 test suites appear normal; the g++ suite dies after over 3000
TP> PASSes, same as it does for others running it on W2K.I wouldn't be
TP> surprised if expect is doing something wrong, but I don't see how these
TP> messages explain what.

are  those messages spontaneous, or they appear every time 'expect' is
running?  do  they  appear in the very beginning of testsuite or after
some  tests  had  run? what version of expect do you have? if you have
cygwin  sources  on  your machine and had built cygwin1.dll from them,
could  you  please try running cygwin's testsuite ('make check' in the
build directory)?

Egor.            mailto:deo@logos-m.ru ICQ 5165414 FidoNet 2:5020/496.19



--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple



--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple

Re: Re: screen echos from cygwin1-20010225.dll

[Christopher Faylor]

On Thu, Mar 08, 2001 at 05:41:04PM -0500, tprinceusa@mindspring.com wrote:
>I have the standard cygwin up to date as done by the standard
>installer, but with the snapshot cygwin1.dll added.  expect 20010117
>was most recently installed.  The first big batch of messages starts
>immediately upon beginning the gcc testsuite, as my posted screen echo
>shows.  I have not watched that make check closely recently; I believe
>it has already completed some instances of expect before this happensl.
>
>I have not attempted to build cygwin1.dll myself for many months, but I
>will try that if it will help.

There is no need to do this unless you want to.  Thanks for the offer,
though.

I think I know what the problem is.  You can expect a fix in the next
week.

Thanks for bringing this to our attention.  As it turns out, I knew about
this problem a while ago and just forgot to do anything about it.  I guess
I have to improve my todo list.

cgf

--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple

Re: Re: screen echos from cygwin1-20010225.dll

[Christopher Faylor]

On Thu, Mar 08, 2001 at 08:28:26PM -0500, Christopher Faylor wrote:
>On Thu, Mar 08, 2001 at 05:41:04PM -0500, tprinceusa@mindspring.com wrote:
>>I have the standard cygwin up to date as done by the standard
>>installer, but with the snapshot cygwin1.dll added.  expect 20010117
>>was most recently installed.  The first big batch of messages starts
>>immediately upon beginning the gcc testsuite, as my posted screen echo
>>shows.  I have not watched that make check closely recently; I believe
>>it has already completed some instances of expect before this happensl.
>>
>>I have not attempted to build cygwin1.dll myself for many months, but I
>>will try that if it will help.
>
>There is no need to do this unless you want to.  Thanks for the offer,
>though.
>
>I think I know what the problem is.  You can expect a fix in the next
>week.

I have checked in a fix for this, I hope.  It should be in the next
snapshot.

cgf

--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple

Re: Re: screen echos from cygwin1-20010225.dll

[Christopher Faylor]

On Wed, Mar 07, 2001 at 11:20:19PM -0800, Tim Prince wrote:
>I don't see these as build errors; maybe I'm missing something.  expect
>runs the same with the 1.1.7 cygwin1.dll and with the post-1.1.8
>snapshots, except for these additional messages.  The results from gcc
>and g77 test suites appear normal; the g++ suite dies after over 3000
>PASSes, same as it does for others running it on W2K.I wouldn't be
>surprised if expect is doing something wrong, but I don't see how these
>messages explain what.

These are diagnostic messages from the cygwin dll itself.  They are
indicating a bug in cygwin.

As I've said, Cygwin is supposed to be silent.  When it prints a message
it indicates that there is a bug in cygwin.

cgf

>----- Original Message -----
>From: "Larry Hall (RFK Partners, Inc)" <lhall@rfk.com>
>To: <tprinceusa@mindspring.com>; <cygwin@cygwin.com>
>Sent: Wednesday, March 07, 2001 10:37 AM
>Subject: Re: Re: screen echos from cygwin1-20010225.dll
>
>
>>I think Chris's point is that this is an error.  Whenever things don't
>>build cleanly, that's an error.  There are no diagnostic messages
>>during a build by default.  You can assume that any message you see
>>indicate a problem that needs to be addressed in some way.
>>
>>
>> Larry Hall                              lhall@rfk.com
>> RFK Partners, Inc.                      http://www.rfk.com
>> 118 Washington Street                   (508) 893-9779 - RFK Office
>> Holliston, MA 01746                     (508) 893-9889 - FAX
>>
>> >
>> > >runtest --tool gcc )
>> > >WARNING: Couldn't find the global config file.
>> > >Test Run By 500 on Wed Mar  7 05:50:38 2001
>> > >Native configuration is i686-pc-cygwin
>> > >
>> > >  === gcc tests ===
>> > >
>> > >Schedule of variations:
>> > >    unix
>> > >
>> > >Running target unix
>> > >Using /usr/share/dejagnu/baseboards/unix.exp as board description
>file for
>> > >target.
>> > >Using /usr/share/dejagnu/config/unix.exp as generic interface file
>for
>> > >target.
>> > >Using /gcc-20010305/gcc/testsuite/config/default.exp as
>> > >tool-and-target-specific interface file.
>> > >Running
>/gcc-20010305/gcc/testsuite/gcc.c-torture/compile/compile.exp ...
>> > >6341600 [main] expect 1324 close_handle: attempt to close protected
>handle
>> > >int tty::make_pipes (fhandler_pty_master *):365(from_pty)
>> > >6394756 [main] expect 1324 close_handle:  by void
>fhandler_base::hclose
>> > >(void *):253(h)
>> > >6437293 [main] expect 1324 close_handle: attempt to close protected
>handle
>> > >int tty::make_pipes (fhandler_pty_master *):358(to_pty)
>> > >6480139 [main] expect 1324 close_handle:  by void
>fhandler_base::hclose
>> > >(void *):253(h)
>
>
>
>--
>Want to unsubscribe from this list?
>Check out: http://cygwin.com/ml/#unsubscribe-simple

-- 
cgf@cygnus.com                        Red Hat, Inc.
http://sources.redhat.com/            http://www.redhat.com/

--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple

Re: Re: screen echos from cygwin1-20010225.dll

[Tim Prince]

I don't see these as build errors; maybe I'm missing something.  expect
runs the same with the 1.1.7 cygwin1.dll and with the post-1.1.8
snapshots, except for these additional messages.  The results from gcc
and g77 test suites appear normal; the g++ suite dies after over 3000
PASSes, same as it does for others running it on W2K.I wouldn't be
surprised if expect is doing something wrong, but I don't see how these
messages explain what.
----- Original Message -----
From: "Larry Hall (RFK Partners, Inc)" <lhall@rfk.com>
To: <tprinceusa@mindspring.com>; <cygwin@cygwin.com>
Sent: Wednesday, March 07, 2001 10:37 AM
Subject: Re: Re: screen echos from cygwin1-20010225.dll


> I think Chris's point is that this is an error.  Whenever things don't
build
> cleanly, that's an error.  There are no diagnostic messages during a
build
> by default.  You can assume that any message you see indicate a
problem that
> needs to be addressed in some way.
>
> Larry Hall                              lhall@rfk.com
> RFK Partners, Inc.                      http://www.rfk.com
> 118 Washington Street                   (508) 893-9779 - RFK Office
> Holliston, MA 01746                     (508) 893-9889 - FAX
>
> >
> > >runtest --tool gcc )
> > >WARNING: Couldn't find the global config file.
> > >Test Run By 500 on Wed Mar  7 05:50:38 2001
> > >Native configuration is i686-pc-cygwin
> > >
> > >  === gcc tests ===
> > >
> > >Schedule of variations:
> > >    unix
> > >
> > >Running target unix
> > >Using /usr/share/dejagnu/baseboards/unix.exp as board description
file for
> > >target.
> > >Using /usr/share/dejagnu/config/unix.exp as generic interface file
for
> > >target.
> > >Using /gcc-20010305/gcc/testsuite/config/default.exp as
> > >tool-and-target-specific interface file.
> > >Running
/gcc-20010305/gcc/testsuite/gcc.c-torture/compile/compile.exp ...
> > >6341600 [main] expect 1324 close_handle: attempt to close protected
handle
> > >int tty::make_pipes (fhandler_pty_master *):365(from_pty)
> > >6394756 [main] expect 1324 close_handle:  by void
fhandler_base::hclose
> > >(void *):253(h)
> > >6437293 [main] expect 1324 close_handle: attempt to close protected
handle
> > >int tty::make_pipes (fhandler_pty_master *):358(to_pty)
> > >6480139 [main] expect 1324 close_handle:  by void
fhandler_base::hclose
> > >(void *):253(h)



--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple

Re: Re: screen echos from cygwin1-20010225.dll

[Larry Hall (RFK Partners, Inc)]

I think Chris's point is that this is an error.  Whenever things don't build
cleanly, that's an error.  There are no diagnostic messages during a build
by default.  You can assume that any message you see indicate a problem that
needs to be addressed in some way.

Larry Hall                              lhall@rfk.com
RFK Partners, Inc.                      http://www.rfk.com
118 Washington Street                   (508) 893-9779 - RFK Office
Holliston, MA 01746                     (508) 893-9889 - FAX


At 01:33 PM 3/7/2001, tprinceusa@mindspring.com wrote:
>You asked why I commented that these snapshots of cygwin1.dll were  better than the 1.1.8 except for tons of warning messages.  If you don't care to give us a hint whether there is a way to turn off such diagnostics, or even whether it points to something which we could work on in expect, so be it.  If you don't want details when someone makes such a comment, I won't answer you in the future.
>
>cygwin@cygwin.com wrote:
>What kind of statement is this?  You're expecting that error messages
>to be intentional?  Are you trying to be purposely annoying?
>
>In case it isn't abundantly clear, this is an error.  Cygwin is not supposed
>to randomly print things to stdout.
>
>cgf
>
> >runtest --tool gcc )
> >WARNING: Couldn't find the global config file.
> >Test Run By 500 on Wed Mar  7 05:50:38 2001
> >Native configuration is i686-pc-cygwin
> >
> >  === gcc tests ===
> >
> >Schedule of variations:
> >    unix
> >
> >Running target unix
> >Using /usr/share/dejagnu/baseboards/unix.exp as board description file for
> >target.
> >Using /usr/share/dejagnu/config/unix.exp as generic interface file for
> >target.
> >Using /gcc-20010305/gcc/testsuite/config/default.exp as
> >tool-and-target-specific interface file.
> >Running /gcc-20010305/gcc/testsuite/gcc.c-torture/compile/compile.exp ...
> >6341600 [main] expect 1324 close_handle: attempt to close protected handle
> >int tty::make_pipes (fhandler_pty_master *):365(from_pty)
> >6394756 [main] expect 1324 close_handle:  by void fhandler_base::hclose
> >(void *):253(h)
> >6437293 [main] expect 1324 close_handle: attempt to close protected handle
> >int tty::make_pipes (fhandler_pty_master *):358(to_pty)
> >6480139 [main] expect 1324 close_handle:  by void fhandler_base::hclose
> >(void *):253(h)
>
>
>--
>Want to unsubscribe from this list?
>Check out: http://cygwin.com/ml/#unsubscribe-simple


--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple

Re: Re: screen echos from cygwin1-20010225.dll

[tprinceusa]

You asked why I commented that these snapshots of cygwin1.dll were  better than the 1.1.8 except for tons of warning messages.  If you don't care to give us a hint whether there is a way to turn off such diagnostics, or even whether it points to something which we could work on in expect, so be it.  If you don't want details when someone makes such a comment, I won't answer you in the future.

cygwin@cygwin.com wrote:
What kind of statement is this?  You're expecting that error messages
to be intentional?  Are you trying to be purposely annoying?

In case it isn't abundantly clear, this is an error.  Cygwin is not supposed
to randomly print things to stdout.

cgf

>runtest --tool gcc )
>WARNING: Couldn't find the global config file.
>Test Run By 500 on Wed Mar  7 05:50:38 2001
>Native configuration is i686-pc-cygwin
>
>  === gcc tests ===
>
>Schedule of variations:
>    unix
>
>Running target unix
>Using /usr/share/dejagnu/baseboards/unix.exp as board description file for
>target.
>Using /usr/share/dejagnu/config/unix.exp as generic interface file for
>target.
>Using /gcc-20010305/gcc/testsuite/config/default.exp as
>tool-and-target-specific interface file.
>Running /gcc-20010305/gcc/testsuite/gcc.c-torture/compile/compile.exp ...
>6341600 [main] expect 1324 close_handle: attempt to close protected handle
>int tty::make_pipes (fhandler_pty_master *):365(from_pty)
>6394756 [main] expect 1324 close_handle:  by void fhandler_base::hclose
>(void *):253(h)
>6437293 [main] expect 1324 close_handle: attempt to close protected handle
>int tty::make_pipes (fhandler_pty_master *):358(to_pty)
>6480139 [main] expect 1324 close_handle:  by void fhandler_base::hclose
>(void *):253(h)


--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple