costi (Constantin Gavrilescu)
- Login: costi
- Email: comisarulmoldovan@gmail.com
- Registered on: 03/27/2015
- Last sign in: 03/27/2015
Issues
| open | closed | Total | |
|---|---|---|---|
| Assigned issues | 0 | 0 | 0 |
| Reported issues | 0 | 1 | 1 |
Activity
03/27/2015
-
10:34 PM Ruby Bug #11009: closed STDOUT status does not get inherited to children processes created with exec
- Actually, the fails this way only in 1.8.7.
Ruby 2.1 child process reports the `STDOUT` as open and uses successfully `STDOUT`, even if the parent closed it, which is also strange, but not as bad. -
- The output of the script is:
~~~
Closing stdout and forking
PARENT STDOUT closed? true
CHILD STDOUT closed? false
Trying to write to STDOUT a test line
Done writing STDOUT. Did you see anything?
-
- When closing `STDOUT`, then `STDOUT.closed?` returns `true`. In a child process started with exec, `STDOUT` is closed but it does `closed?` returns `false`.
Also, in the child process, writing to `STDOUT` fails silently, so the user h...