From: Jan Jaeger <pa3efu@yahoo.com>
To: cygwin@cygwin.com
Subject: setvbuf/setlinebuf issue
Date: Tue, 16 Sep 2003 19:18:00 -0000 [thread overview]
Message-ID: <20030916191331.85685.qmail@web40017.mail.yahoo.com> (raw)
Hi List,
I am one of the developers of the hercules emulator
(http://www.conmicro.cx/hercules), and it seems that
we have hit a problem with setvbuf in more recent
cygwin versions.
We capture all standard output by means of redirecting
stdout to a pipe, which is subsequently read by a
logger function. (printf() to stdout, which then goes
to the pipe, read() by the logger function from the
pipe)
We have always used setvbuf(stdout, NULL, _IOLBF, 0)
to ensure that each line is read by the logger as it
is written.
However this has now stopped working in the current
release of cygwin, adding a fflush() after every
printf() bypasses the error, but at the moment setvbuf
does not seem to work correctly for us.
What I find somewhat odd is that this only happens
when I recompile under the current cygwin. If I use
an older binrary (created on backlevel cygwin) then
all works fine.
Has anyone experienced any similar problems with
streams buffering?
Thanks and regards,
Jan Jaeger
__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com
--
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/
next reply other threads:[~2003-09-16 19:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-16 19:18 Jan Jaeger [this message]
2003-09-16 20:04 ` Christopher Faylor
2003-09-17 17:57 Jan Jaeger
2003-09-17 18:39 Brian Ford
2003-09-17 21:39 ` Christopher Faylor
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030916191331.85685.qmail@web40017.mail.yahoo.com \
--to=pa3efu@yahoo.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).