470,810 Members | 865 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 470,810 developers. It's quick & easy.

writing to a pipe on win32

Hi experts,
I need to write a perl script that will be called from a series of
executables chained thru pipes that read from STDIN and writes to
STDOUT. The following code works fine under regular circumstance. But
when there is a error down the pipe in one of the executables, the
pipe closes and then this script just exits. It does not print line
14. The troublesome line is line number 17. If I comment it out, the
script completes. From my very little perl knowledge, I was thinking
that in line 17, when we call "print $_" and the pipe broke due to the
error in another executable, it would generate SIGPIPE, but I get no
signal. Does SIGPIPE work on windows ?

1 sub signalhandler
2 {
3 print STDERR "*Received a SIG$_[0]\n";
4 }

5 my $Tmp_File = "c:/test_dir/testFile";

6 open(IN_FILE, ">$Tmp_File") || die "Open file error: $!";
7 binmode (IN_FILE);

8 while (<STDIN>) {
9 print IN_FILE ;
10 }
11 close(IN_FILE);

12 use sigtrap qw{handler signalhandler normal-signals
error-signals};

13 open(OUT_FILE, "$some_other_executable $Tmp_File |") || die
"Fork error: $!";
14 print STDERR "Opened file OUT_FILE!!\n";
15 binmode (OUT_FILE);
16 while (<OUT_FILE>) {
17 print $_;
18 }
19 unlink ($Tmp_File) || die "Remove file error: $!";

Thanks in advance.

Momena
Jul 19 '05 #1
1 5088
mo*****@yahoo.com (momena) wrote in message news:<1a**************************@posting.google. com>...
Hi experts,
I need to write a perl script that will be called from a series of
executables chained thru pipes that read from STDIN and writes to
STDOUT. The following code works fine under regular circumstance. But
when there is a error down the pipe in one of the executables, the
pipe closes and then this script just exits. It does not print line
14. The troublesome line is line number 17. If I comment it out, the
script completes. From my very little perl knowledge, I was thinking
that in line 17, when we call "print $_" and the pipe broke due to the
error in another executable, it would generate SIGPIPE, but I get no
signal. Does SIGPIPE work on windows ?

1 sub signalhandler
2 {
3 print STDERR "*Received a SIG$_[0]\n";
4 }

5 my $Tmp_File = "c:/test_dir/testFile";

6 open(IN_FILE, ">$Tmp_File") || die "Open file error: $!";
7 binmode (IN_FILE);

8 while (<STDIN>) {
9 print IN_FILE ;
10 }
11 close(IN_FILE);

12 use sigtrap qw{handler signalhandler normal-signals
error-signals};

13 open(OUT_FILE, "$some_other_executable $Tmp_File |") || die
"Fork error: $!";
14 print STDERR "Opened file OUT_FILE!!\n";
15 binmode (OUT_FILE);
16 while (<OUT_FILE>) {
17 print $_;
18 }
19 unlink ($Tmp_File) || die "Remove file error: $!";

Thanks in advance.

Momena


I ran it on unix (hpux) and I get SIGTERM, not SIGPIPE. Now that I
think about it again, it makes sense not to get a SIGPIPE, because I
am not directly writing to a pipe in line 17, even though other end os
STDOUT is a pipe. But in windows I get no signals. It seems very wrong
to me. Any comments ?
Jul 19 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

13 posts views Thread by j. del | last post: by
8 posts views Thread by mojozoox | last post: by
3 posts views Thread by EricR | last post: by
6 posts views Thread by placid | last post: by
4 posts views Thread by Gigs_ | last post: by
2 posts views Thread by MAx | last post: by
reply views Thread by mihailmihai484 | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.