Worker: I already redirect STDERR and STDOUT into buffers (local scalars) in every worker so that families of computations have their results contiguously located in the final report. I tried this as well as a bidirectional pipe (Bidirectional Communication with Yourself) but it fails to catch the error output by the child w/o the explicit command line redirect. I suppose I could implement it with IPC::Open3.
Utility: While the utility is developed by my group, I am not the programmer responsible. It's a C binary (heavy computation) and I philosophically I think it uses channels correctly. Plus the large number of issues my testing script has uncovered in the previous month has not left me as that gentleman's favorite person.
In reply to Re^4: Handling badly behaved system calls in threads
by kennethk
in thread Handling badly behaved system calls in threads
by kennethk
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |