test.txt contains traces from all the threads making debugging it more difficult.
I strongly suggest that you add some perl level tracing in the scripts that uses threads->tid; as (the first) part of each trace message.
Trying to debug threaded apps with traces that mix the thread's output together without identification is a fool's errand.
In reply to Re: Perl 5.8.8 on Windows, Hang in I/O operations using perlembed
by BrowserUk
in thread Perl 5.8.8 on Windows, Hang in I/O operations using perlembed
by perlstart_08
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |