# Re: getting stdout and stderr for system calls on windows

**URL:** <https://www.ruby-forum.com/t/re-getting-stdout-and-stderr-for-system-calls-on-windows/52998>\
**Category:** Ruby\
**Created:** [November 23, 2005, 5:14pm UTC](https://www.ruby-forum.com/t/re-getting-stdout-and-stderr-for-system-calls-on-windows/52998 "2005-11-23T17:14:47Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Daniel.Berger](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/d/ac8455/32.png) [@Daniel.Berger](https://www.ruby-forum.com/u/Daniel.Berger)\
**Post date:** [November 23, 2005, 5:14pm UTC](https://www.ruby-forum.com/t/re-getting-stdout-and-stderr-for-system-calls-on-windows/52998/1 "2005-11-23T17:14:47Z")

</div>

> want to capture stdout and stderr as well as the return value  
> from dmake. Normally I would do it using Daniel B.'s  
> win32-popen3, but I have a  
> Windows Installer Ruby with VC++6.0 which nastily gives me a segfault  
> (properly documented in the README, but still a segfault 🙂  
> ). Recompiling Ruby is a no-no and changing VC compiler also a no-no.

If anyone knows of a magic compatibility switch to cl or link that will  
prevent this, I’m all ears. 🙂

Dan