If I change 373 in "print $parent "exit now\r\n\r" x 373;" to 745 (744 hangs) it works.
C:\Documents and Settings\Owner\Desktop>perl -e "print (length(\"exit +now\r\n\r\ " x 745).\"\n\");" 8195
I guess is somewhat explained by the hung C callstack of the child of my first script.
ntdll.dll!_KiFastSystemCallRet@0() ntdll.dll!_NtReadFile@36() + 0xc kernel32.dll!_ReadFile@20() + 0x67 > msvcr71.dll!_read_lk(int fh=3, void * buf=0x00963fec, unsigned in +t cnt=8192) Line 154 + 0x15 C msvcr71.dll!_read(int fh=3, void * buf=0x00963fec, unsigned int c +nt=8192) Line 75 + 0xc C perl517.dll!win32_read(int fd=3, void * buf=0x00963fec, unsigned +int cnt=8192) Line 3209 + 0x12 C perl517.dll!PerlLIORead(IPerlLIO * piPerl=0x00346654, int handle= +3, void * buffer=0x00963fec, unsigned int count=8192) Line 1033 + 0x +11 C++ perl517.dll!PerlIOUnix_read(interpreter * my_perl=0x0093502c, _Pe +rlIO * * f=0x00935e8c, void * vbuf=0x00963fec, unsigned int count=819 +2) Line 2789 + 0x22 C perl517.dll!Perl_PerlIO_read(interpreter * my_perl=0x0093502c, _P +erlIO * * f=0x00935e8c, void * vbuf=0x00963fec, unsigned int count=81 +92) Line 1679 + 0x3e C perl517.dll!PerlIOBuf_fill(interpreter * my_perl=0x0093502c, _Per +lIO * * f=0x00935aa4) Line 4033 + 0x1b C perl517.dll!Perl_PerlIO_fill(interpreter * my_perl=0x0093502c, _P +erlIO * * f=0x00935aa4) Line 1776 + 0x36 C perl517.dll!PerlIOBase_read(interpreter * my_perl=0x0093502c, _Pe +rlIO * * f=0x00935aa4, void * vbuf=0x0095b49c, unsigned int count=1) + Line 2170 + 0xd C perl517.dll!PerlIOBuf_read(interpreter * my_perl=0x0093502c, _Per +lIO * * f=0x00935aa4, void * vbuf=0x0095b49c, unsigned int count=1) +Line 4054 + 0x15 C perl517.dll!Perl_PerlIO_read(interpreter * my_perl=0x0093502c, _P +erlIO * * f=0x00935aa4, void * vbuf=0x0095b49c, unsigned int count=1) + Line 1679 + 0x3e C perl517.dll!Perl_pp_sysread(interpreter * my_perl=0x0093502c) Li +ne 1775 + 0x18 C perl517.dll!Perl_runops_debug(interpreter * my_perl=0x0093502c) +Line 2126 + 0xd C perl517.dll!win32_start_child(void * arg=0x0093502c) Line 1742 + + 0xd C++ kernel32.dll!_BaseThreadStart@8() + 0x37
0x2000/8192 was passed as the read amount to ReadFile. Does anyone know what should have happened on Windows? What happens on Unix? 8192 read also? or it will still succeed for POSIX reasons? is the 8192 read length a bug or correct?

In reply to Re^2: pipe fork win32 by bulk88
in thread pipe fork win32 by bulk88

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.