Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender:	cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To:	mailing list cygwin AT sourceware DOT cygnus DOT com
Message-ID:	<75F8791C7793D211B64D080036DE1504151C81@milton.sonosight.com>
From:	"Stewart, Wayne" <wayne DOT stewart AT sonosite DOT com>
To:	"'earnie_boyd AT yahoo DOT com'" <earnie_boyd AT yahoo DOT com>,
	"'cygwin AT sourceware DOT cygnus DOT com'" <cygwin AT sourceware DOT cygnus DOT com>
Subject:	Problems with stdio & stderr
Date:	Thu, 29 Apr 1999 08:56:07 -0700
MIME-Version:	1.0
X-Mailer:	Internet Mail Service (5.5.2448.0)

Earnie,

Thanks, but that did not make a difference.
(I didn't have a CYGWIN env var set, so I
believe I was running with "notty" anyway,
if that's the default.)  Here's a summary
of the circumstances under which
stdio/stderr output is seen from the Win32
DLL:

    CYGWIN=                    tty    notty
    ---------------------      ---    -----
    DOS box                    yes     yes
    Cygwin (bash) box           no     yes
    Emacs (bash) shell          no      no
    Cygwin dejagnu/expect       no      no

In the emacs case, tty returns "not a tty".

(Just a thought: this problem seems similar
to that of the recent thread on Cygwin PATH
env var vs. Win32 PATH env var.)

Any thoughts on whether the callback workaround
will work?  What if my callback needs to take
a variable # of args like printf.  Will a
Win32 call pass the right type of va_list to
a Cygwin function?

Is there any documentation on what changes
were made in cygtclsh80/expect/dejagnu to
port them to Cygwin?  Particularly, how the
stuff that expect does with tty's was
implemented?

Thanks,
    Wayne


> -----Original Message-----
> From: Earnie Boyd [mailto:earnie_boyd AT yahoo DOT com]
> Sent: Wednesday, April 28, 1999 6:55 PM
> To: Stewart, Wayne; 'cygwin AT sourceware DOT cygnus DOT com'
> Subject: Re: Problems with maillist archive searches
> 
> 
> 
> SET CYGWIN=notty
> 
> The communication channels between cygwin and non-cygwin 
> binaries must be set
> this way.
> 
> Earnie.
> --- "Stewart, Wayne" <wayne DOT stewart AT sonosite DOT com> wrote:
> > 
> > 
> > I have a cygwin program that calls
> > into a Windows DLL.  The windows
> > DLL writes to stdout & stderr.
> > The Win32 stdout/stderr appear to
> > be different than the CygWin
> > stdout/stderr.  For instance, if
> > I run said program in an NTemacs
> > shell (bash), I see the cygwin
> > stdout/stderr writes but the
> > ones from the Win32 DLL have
> > disappeared, even though they
> > were there in a regular bash
> > shell and/or DOS box.  Likewise
> > dejagnu/expect does not see the
> > Win32 stdout/stderr text.
> > What's going on here?  Can I
> > write to Cygwin's stdout/stderr
> > from within my Win32 DLL, so that
> > emacs & dejagnu will see all my
> > program's output?  Perhaps I could
> > pass a callback function into the
> > Win32 DLL to do the writes using
> > Cygwin's functions & file descriptors?
> > 

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com

- Raw text -