X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=1.4 required=5.0	tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW
X-Spam-Check-By: sourceware.org
MIME-Version: 1.0
In-Reply-To: <4EE27335.9070106@cygwin.com>
References: <CAGVbXL7pXn5BZSNXNJKMTbGUOQzAhGBOZwxdsPGa-bucQf6dBg AT mail DOT gmail DOT com>	<4EE27335 DOT 9070106 AT cygwin DOT com>
Date: Fri, 9 Dec 2011 16:12:34 -0800
Message-ID: <CAGVbXL5_rPrPGK8Z8Yfr0yKyqCOSOgoXX6keNEG_7igKh_Y6eA@mail.gmail.com>
Subject: Re: stdout output missing, but redirecting works
From: Brian Craft <bcboy AT thecraftstudio DOT com>
To: cygwin AT cygwin DOT com
Content-Type: text/plain; charset=ISO-8859-1
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
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
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id pBA0Cx0t006559

On Fri, Dec 9, 2011 at 12:44 PM, Larry Hall (Cygwin) wrote:
> On 12/9/2011 2:47 PM, Brian Craft wrote:
>>
>> I compiled a program yesterday which output some lines to stdout. It
>> appeared to be working. Running it today, I get nothing on stdout.
>> However, if I redirect stdout to a file, the correct output appears in
>> the file. E.g.
>>
>> # no output
>> ./foo
>> # "hello world" in bar
>> ./foo>  bar
>>
>>
>> In between yesterday and today, I've rebooted and run rebaseall, so
>> perhaps one of those is responsible for the change.
>>
>> Any suggestions?
>
>
> Sounds like buffering to me.  Is this program compiled with Cygwin's gcc
> or something else?  What kind of terminal are you running it in?  Same one
> as yesterday?

Cygwin's g++. The default cygwin terminal.

Another bit of data: if I explicitly redirect the output to /dev/tty0,
I also get no output. E.g.

# outputs "hello"
echo hello > /dev/tty0
# no output
./foo > /dev/tty0

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