Bug #55164 for IO-CaptureOutput: Bad joining of STDERR + STDOUT in windows

Wed Mar 03 00:51:37 2010 alexandrfedorov [...] gmail.com - Ticket created

Subject:

Bad joining of STDERR + STDOUT in windows

I'm trying to execute windows utility "wmic", if success it's return data in utf-16 encoding, in some sort of errors - utf-16 too, and sometimes in ANSI encoding. When error is going with utf-16 encoding, BOM header in printed to STDOUT and all that remains is printed to STDERR. When using qxx sub BOM header - don't join to STDERR stream and i can't simply decode that string, please repair this.

Wed Mar 03 08:28:27 2010 dagolden [...] cpan.org - Correspondence added

Subject:	Re: [rt.cpan.org #55164] Bad joining of STDERR + STDOUT in windows
Date:	Wed, 3 Mar 2010 07:27:01 -0500
To:	bug-IO-CaptureOutput [...] rt.cpan.org
From:	David Golden <dagolden [...] cpan.org>

On Wed, Mar 3, 2010 at 12:51 AM, Alexandr Fedorov via RT <bug-IO-CaptureOutput@rt.cpan.org> wrote: Show quoted text

> I'm trying to execute windows utility "wmic", if success it's return > data in utf-16 encoding, in some sort of errors - utf-16 too, and > sometimes in ANSI encoding. > When error is going with utf-16 encoding, BOM header in printed to > STDOUT and all that remains is printed to STDERR. When using qxx sub BOM > header - don't join to STDERR stream and i can't simply decode that > string, please repair this.

IO::CaptureOutput is not getting active support these days as I've been working on a replacement called Capture::Tiny. Capture::Tiny has some better support for utf, but I don't know if it will solve your particular problem. Would you mind trying it and letting me know? Also, per your other ticket, getting quoting right on Windows is hard. I suggest you try either IPC::System::Simple or IPC::Cmd and see if they get it right. Then, with Capture:Tiny, your code would be like this: use IPC::System::Simple 'systemx'; use Capture::Tiny 'capture'; my ($output, $error) = capture { systemx($cmd, @args) }; You might also want to read http://www.perlmonks.org/?node_id=722963 which suggests that piping wmic to another process forces ANSI output, which might help you. -- David

Wed Mar 03 08:28:28 2010 The RT System itself - Status changed from 'new' to 'open'

Wed Mar 17 16:19:01 2010 alexandrfedorov [...] gmail.com - Correspondence added

Срд Мар 03 08:28:27 2010, DAGOLDEN писал: Show quoted text

> On Wed, Mar 3, 2010 at 12:51 AM, Alexandr Fedorov via RT

Show quoted text

> use IPC::System::Simple 'systemx'; > use Capture::Tiny 'capture'; > my ($output, $error) = capture { systemx($cmd, @args) };

I tried this and many other variants... There is some problem with your module and IPC::System::Simple, 1. My script in utf8 encoding 2. I'm using utf8 pragma 3. I'm running something like this: $rslt = capture_merged { systemx('cmd','/c',encode 'cp1251','echo Не работает'); }; (important part - with cyrillic letters (in utf8 encoding)) 4. script silently dies If i add: binmode $_,':encoding(866)' for *STDOUT,*STDERR script works. Can you explain for me this? With Perl's "system" your module works well.

Wed Mar 17 23:15:26 2010 dagolden [...] cpan.org - Correspondence added

CC:	Paul Jamieson Fenwick <pjf [...] cpan.org>
Subject:	Re: [rt.cpan.org #55164] Bad joining of STDERR + STDOUT in windows
Date:	Wed, 17 Mar 2010 23:14:09 -0400
To:	bug-IO-CaptureOutput [...] rt.cpan.org
From:	David Golden <dagolden [...] cpan.org>

Alexandr, I have to admit I'm stumped. So I'm copying the author of IPC::System::Simple in the hopes that he has some ideas about what is happening. Paul, please see the conversation below and/or the original RT ticket. It seems like IPC::System::Simple might be doing something to the output handles. Regards, -- David On Wed, Mar 17, 2010 at 4:19 PM, Alexandr Fedorov via RT <bug-IO-CaptureOutput@rt.cpan.org> wrote: Show quoted text

> Queue: IO-CaptureOutput > Ticket <URL: https://rt.cpan.org/Ticket/Display.html?id=55164 > > > Срд Мар 03 08:28:27 2010, DAGOLDEN писал:

>> On Wed, Mar 3, 2010 at 12:51 AM, Alexandr Fedorov via RT

>

>> use IPC::System::Simple 'systemx'; >> use Capture::Tiny 'capture'; >> my ($output, $error) = capture { systemx($cmd, @args) };

> > I tried this and many other variants... There is some problem with your > module and IPC::System::Simple, > 1. My script in utf8 encoding > 2. I'm using utf8 pragma > 3. I'm running something like this: > > $rslt = capture_merged { > systemx('cmd','/c',encode 'cp1251','echo Не работает'); > }; > > (important part - with cyrillic letters (in utf8 encoding)) > 4. script silently dies > > If i add: > binmode $_,':encoding(866)' for *STDOUT,*STDERR > > script works. > Can you explain for me this? > > With Perl's "system" your module works well. >

Thu Mar 18 21:11:53 2010 PJF [...] cpan.org - Correspondence added

G'day Alexandr / David, On Wed Mar 17 23:15:26 2010, DAGOLDEN wrote: Show quoted text

> Paul, please see the conversation below and/or the original RT ticket. > It seems like IPC::System::Simple might be doing something to the > output handles.

If we were using IPC::System::Simple's capture/capturex here, then I'd say yes absolutely weird things are happening to output filehandles. But we're not. We're using systemx(), and letting Capture::Tiny grab the output. For systemx() on Windows, we use Win32::Process::Create to spawn the command, but otherwise don't touch filehandles at all. There is a bit of extra poking around to try and determine where that could should be ($ENV{PATH} searching is normally done by the shell, but none of that involves changing filehandles. I'd be *very* interested to see if a call to Win32::Process::Create() has the same issues, since that's what I'm fundamentally using underneath. Best wishes, Paul

Wed Jan 28 20:18:56 2015 dagolden [...] cpan.org - Correspondence added

Ticket migrated to github as https://github.com/dagolden/IO-CaptureOutput/issues/8

Wed Jan 28 20:19:02 2015 dagolden [...] cpan.org - Status changed from 'open' to 'resolved'

Bug #55164 for IO-CaptureOutput: Bad joining of STDERR + STDOUT in windows

Preferred bug tracker