* stdout output missing, but redirecting works
@ 2011-12-09 19:48 Brian Craft
2011-12-09 20:45 ` Larry Hall (Cygwin)
0 siblings, 1 reply; 4+ messages in thread
From: Brian Craft @ 2011-12-09 19:48 UTC (permalink / raw)
To: cygwin
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?
--
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
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: stdout output missing, but redirecting works
2011-12-09 19:48 stdout output missing, but redirecting works Brian Craft
@ 2011-12-09 20:45 ` Larry Hall (Cygwin)
2011-12-10 0:12 ` Brian Craft
0 siblings, 1 reply; 4+ messages in thread
From: Larry Hall (Cygwin) @ 2011-12-09 20:45 UTC (permalink / raw)
To: cygwin
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?
--
Larry
_____________________________________________________________________
A: Yes.
> Q: Are you sure?
>> A: Because it reverses the logical flow of conversation.
>>> Q: Why is top posting annoying in email?
--
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
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: stdout output missing, but redirecting works
2011-12-09 20:45 ` Larry Hall (Cygwin)
@ 2011-12-10 0:12 ` Brian Craft
2011-12-10 1:45 ` Larry Hall (Cygwin)
0 siblings, 1 reply; 4+ messages in thread
From: Brian Craft @ 2011-12-10 0:12 UTC (permalink / raw)
To: cygwin
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
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: stdout output missing, but redirecting works
2011-12-10 0:12 ` Brian Craft
@ 2011-12-10 1:45 ` Larry Hall (Cygwin)
0 siblings, 0 replies; 4+ messages in thread
From: Larry Hall (Cygwin) @ 2011-12-10 1:45 UTC (permalink / raw)
To: cygwin
On 12/9/2011 7:12 PM, Brian Craft wrote:
> 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
Then my next WAG is BLODA - <http://cygwin.com/acronyms/#BLODA>. If that's
not it, I recommend a full report - <http://cygwin.com/problems.html>.
--
Larry
_____________________________________________________________________
A: Yes.
> Q: Are you sure?
>> A: Because it reverses the logical flow of conversation.
>>> Q: Why is top posting annoying in email?
--
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
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2011-12-10 1:45 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2011-12-09 19:48 stdout output missing, but redirecting works Brian Craft
2011-12-09 20:45 ` Larry Hall (Cygwin)
2011-12-10 0:12 ` Brian Craft
2011-12-10 1:45 ` Larry Hall (Cygwin)
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).