X-Spam-Check-By:	sourceware.org
Date:	Wed, 11 Jan 2006 11:58:07 -0500 (EST)
From:	Igor Peshansky <pechtcha AT cs DOT nyu DOT edu>
Reply-To:	cygwin AT cygwin DOT com
To:	Russell K Montgomery <work AT russellonthenet DOT com>
cc:	cygwin AT cygwin DOT com
Subject:	Re: New installation does not connect stdout to terminal
In-Reply-To:	<43C53448.3090004@russellonthenet.com>
Message-ID:	<Pine.GSO.4.63.0601111149360.9317@access1.cims.nyu.edu>
References:	<43C53448 DOT 3090004 AT russellonthenet DOT com>
MIME-Version:	1.0
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Unsubscribe:	<mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com

On Wed, 11 Jan 2006, Russell K Montgomery wrote:

> I have installed cygwin on a new Windows XP box and when I run Cygwin I
> do not get output from commands on the terminal.  The only way I can get
> the output is to redirect stdout to stderr "ls -l 1>&2"
>
> I have used Cygwin for several years on Windows 98 and for the past year
> on another Windows XP box but have not seen any behavior like this.  I
> have searched the archives and not found any reports that are similar to
> this behavior.  Have I overlooked something?

No, this is something new (and weird).  First, can you try a snapshot (see
<http://cygwin.com/snapshots> for download and installation instructions)
and report if it fixes the problem for you?  The Cygwin developers are
very close[1] to releasing 1.5.19, so any testing of snapshots is helpful.

A WAG: does "/bin/ls -l" have the same problem?

If the snapshot doesn't fix your problem, some more information would be
needed for us to try reproducing this: are you running the command from a
bash shell, from rxvt, from a CMD prompt, or somewhere else?  Does it fail
for all commands (e.g., time)?  When you run a command that outputs to
both stdout and stderr, do you only see stderr output?  Do you see the
output of Windows commands (e.g., "net")?  If you have access to a machine
with the same DLL version that doesn't exhibit this problem, could you
please run the command under "strace" on both machines (i.e., run
"/bin/strace -o ls.strace /bin/ls -l") and compare the output?

FWIW, your cygcheck output looks ok.
HTH,
	Igor
[1] <http://cygwin.com/ml/cygwin/2006-01/msg00503.html>
-- 
				http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_	    pechtcha AT cs DOT nyu DOT edu | igor AT watson DOT ibm DOT com
ZZZzz /,`.-'`'    -.  ;-;;,_		Igor Peshansky, Ph.D. (name changed!)
     |,4-  ) )-,_. ,\ (  `'-'		old name: Igor Pechtchanski
    '---''(_/--'  `-'\_) fL	a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

"Las! je suis sot... -Mais non, tu ne l'es pas, puisque tu t'en rends compte."
"But no -- you are no fool; you call yourself a fool, there's proof enough in
that!" -- Rostand, "Cyrano de Bergerac"


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -