[Octave-bug-tracker] [bug #49211] "test syscall" often hangs on Windows, needs reliable waitpid implementation

[Markus Mützel]

Follow-up Comment #11, bug #49211 (project octave):

Looks like I didn't attach the patch last time.

Re-reading the comments again, I'm no longer sure if I correctly got the point
of this bug.
Should "waitpid" implicitly close the input and output stream of the process
and thereby indicate that the child process can terminate? Otherwise, I would
expect it to block indefinitely if the child process never terminates.
It looks like the general expectation is that it should not block in this
case...
What is the expected behavior?


(file #49145)
    _______________________________________________________

Additional Item Attachment:

File name: bug49211_waitpid_win32.patch   Size:1 KB
    <https://savannah.gnu.org/file/bug49211_waitpid_win32.patch?file_id=49145>



    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?49211>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/