Does it work if you make a standalone script which just calls Win32::... and then from a second script you shell out to it while you capture its stdout? For capture you will have another choice IPC::Run3 which runs a system command and captures its stdout. It's a shot in the dark as I don't have these windows and can not understand why it is not captured in the first place. Plus it is ugly, it is not realtime and it shells out to another Perl script.
If you feel hackish then you could patch the XS file of Win32::... https://metacpan.org/source/KXJ/Win32-Process-CpuUsage-0.02/CpuUsage.xs to accept one additional parameter: an output filehandle/filename. And replace all printf() with PerlIO_printf(FH, "..."); (seriously untested). But before you climb down that hole of daemons see if replacing with PerlIO_printf(PerlIO_stdout(), "..."); captures the stdout. Because if it can't capture stdout, they are probably talking about 2 different stdouts. Perhaps someone more knowledgable can shed some light to it.
In reply to Re^3: Win32::Process::CpuUsage: Redirect output?
by bliako
in thread Win32::Process::CpuUsage: Redirect output?
by Bloehdian
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |