Regression problem in cygwin1.5.18 and Perl 5.8.6/7

Regression problem in cygwin1.5.18 and Perl 5.8.6/7

[Jurgen Defurne]

Here is a description of my problem. I have two different
installations of Cygwin on different systems :

System 1                      System 2
--------                      --------
cygwin 1.5.11-1               cygwin 1.5.18-1
perl   5.8.5-3                perl   5.8.6-4 (or 5.8.7-..)
Windows 2000                  Windows 2003 Server
Windows XP

I have certain programs which run the following code (very condensed)
as a wrapper program :

    open $proc, "$cmd|";

    while (<$proc>) {
          # E.g.
          print $_;
    }

    close $proc;

Under system 1 (the old system) this does what it must do, regardless
if I run Cygwin programs or Windows programs. I can catch the output
of the subprocess and do something with it in parallel in the 'while'
loop (eg. write the output to a log file, and to STDOUT and process it
to extract data).

I have now installed a new environment on Windows 2003 server,
and what now happens is that the output of the started process
is only read and processed after the subprocess terminates.

Nothing else has changed, the scripts which do all the work
are exactly the same.

I have tested the above code on both systems and watched the
processes with procexp. What strikes me as odd is that on the first
system have a process tree like this :

    perl
    sh
        sh
            perl (In case I start ActiveState Perl here)

On the second system I have a process tree like :

    perl
    sh
        perl (like above)

This issue is not blocking for me, because I can run the necessary
programs without my Perl wrapper, but the wrapper adds functionality
which cannot be added to the program being run.

Any ideas ?

Regards,

Jurgen

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Regression problem in cygwin1.5.18 and Perl 5.8.6/7

[Jurgen Defurne]

Repost. It is not that urgent, but it would be nice to get some feedback,
even if it is only to say that I should maybe upgrade to cygwin 1.5.19.

Thanks.

Jurgen









Jurgen Defurne <jurgen.defurne+FromInternet@philips.com> 
Sent by:
cygwin-owner@cygwin.com
2005-10-06 02:48 PM
Please respond to
Jurgen Defurne/BRG/CE/PHILIPS@PHILIPS


To
cygwin@cygwin.com
cc

Subject
Regression problem in cygwin1.5.18 and Perl 5.8.6/7
Classification







Here is a description of my problem. I have two different
installations of Cygwin on different systems :

System 1                      System 2
--------                      --------
cygwin 1.5.11-1               cygwin 1.5.18-1
perl   5.8.5-3                perl   5.8.6-4 (or 5.8.7-..)
Windows 2000                  Windows 2003 Server
Windows XP

I have certain programs which run the following code (very condensed)
as a wrapper program :

    open $proc, "$cmd|";

    while (<$proc>) {
          # E.g.
          print $_;
    }

    close $proc;

Under system 1 (the old system) this does what it must do, regardless
if I run Cygwin programs or Windows programs. I can catch the output
of the subprocess and do something with it in parallel in the 'while'
loop (eg. write the output to a log file, and to STDOUT and process it
to extract data).

I have now installed a new environment on Windows 2003 server,
and what now happens is that the output of the started process
is only read and processed after the subprocess terminates.

Nothing else has changed, the scripts which do all the work
are exactly the same.

I have tested the above code on both systems and watched the
processes with procexp. What strikes me as odd is that on the first
system have a process tree like this :

    perl
    sh
        sh
            perl (In case I start ActiveState Perl here)

On the second system I have a process tree like :

    perl
    sh
        perl (like above)

This issue is not blocking for me, because I can run the necessary
programs without my Perl wrapper, but the wrapper adds functionality
which cannot be added to the program being run.

Any ideas ?

Regards,

Jurgen

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/




--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: Regression problem in cygwin1.5.18 and Perl 5.8.6/7

[Larry Hall (Cygwin)]

Jurgen Defurne wrote:
> Repost. It is not that urgent, but it would be nice to get some feedback,
> even if it is only to say that I should maybe upgrade to cygwin 1.5.19.


Well, you could always try that - <http://cygwin.com/snapshots/>.  The other
possibility is to upgrade your W2K/XP machine to the 1.5.18 version of the
cygwin package and see if you see the same behavior.  The information you've
given so far doesn't eliminate the possibility of a W2K3 bug of some kind.


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

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: Regression problem in cygwin1.5.18 and Perl 5.8.6/7

[Gerrit P. Haase]

Jurgen Defurne wrote:

> Subject
> Regression problem in cygwin1.5.18 and Perl 5.8.6/7
> Classification

[...]

> Any ideas ?

Could test the same with a recent Cygwin snapshot please.
http://cygwin.com/snapshots
And please include more information in reports like described on
http://cygwin.com/problems


Thanks,
Gerrit
-- 
=^..^=


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: Regression problem in cygwin1.5.18 and Perl 5.8.6/7

[Jurgen Defurne]

I have found time to install a fresh Cygwin setup
on a Windows 2000 machine, where I did not have
the previously described problem (three years of
production service).

I wrote a wrapper script which executes the

open $proc, "process|";
while (<$proc>) {
        print $_;
}
close $proc;

loop on an external program.

I used three external programs, one Perl script, one bash
script (both Cygwin related), and one using our much used
Continuus application (Windows command line program).

I had the following three configurations :

System 1           System 2            System 3
W2K3 Server        W2K Server          W2K Server
Cygwin 1.5.18-1    Cygwin 1.5.18.-1    Cygwin 1.5.11-1

On all systems, executing a Cygwin related program
gives the right behavior, that is, as soon as the
file descriptor is ready, a line is read and printed.

Only on system 3, which uses an older version of Cygwin,
this behaviour is correct for the Windows command line
program.

It also has nothing to do with the installation of
Continuus, because the installations on System 2 and 3
have been running for years without problems.

So, first of all, I will try with an upgrade of the
cygwin1.dll.

If this does not help, what can I do more to help you
help me ?

Regards,

Jurgen









"Larry Hall (Cygwin)" <reply-to-list-only-lh@cygwin.com> 
Sent by:
cygwin-owner@cygwin.com
2005-10-10 07:39 PM
Please respond to
cygwin@cygwin.com


To
Jurgen Defurne/BRG/CE/PHILIPS@PHILIPS
cc
cygwin@cygwin.com
Subject
Re: Regression problem in cygwin1.5.18 and Perl 5.8.6/7
Classification







Jurgen Defurne wrote:
> Repost. It is not that urgent, but it would be nice to get some 
feedback,
> even if it is only to say that I should maybe upgrade to cygwin 1.5.19.


Well, you could always try that - <http://cygwin.com/snapshots/>.  The 
other
possibility is to upgrade your W2K/XP machine to the 1.5.18 version of the
cygwin package and see if you see the same behavior.  The information 
you've
given so far doesn't eliminate the possibility of a W2K3 bug of some kind.


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

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/




--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/