the exit value after termination is 141, which means nothing to me.
Then perhaps you should read about $? ?
If I change the print statement to print {$proc->stdin} "text\n" the it appears as if perl tries to run the statement twice!
No, it is just that in print {$proc->stdin} "text\n" there are two statements in that one line. The braces actually constitute a block and so $proc->stdin is a full statement, not just an expression. So the debugger stops for that statement first and then stops for the print statement after that.
But back to your primary question. The reason printing to a pipe usually causes a process to exit is because all readers of that pipe have now closed their handle (usually because they have exit()ed) and so the writing process gets sent SIGPIPE. This behavior should be mentioned briefly in "man 2 write" and should be covered more extensively by "man 7 pipe".
And your exit value confirms that this is the cause in your specific case.
- tye
In reply to Re: Unexpected termination on "print" (pipe)
by tye
in thread Unexpected termination on "print"
by mlawren
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |