On Mar 13 12:06, Corinna Vinschen wrote:
> On Mar 12 16:41, Kaz Kylheku wrote:
> > On 12.03.2016 14:29, Corinna Vinschen wrote:
> > >I do now. Basically it's setvbuf screwing up the internal flags in the
> > >FILE structure. I took the liberty to update newlib's setvbuf to the
> > >OpenBSD versio
On Mar 12 16:41, Kaz Kylheku wrote:
> On 12.03.2016 14:29, Corinna Vinschen wrote:
> >I do now. Basically it's setvbuf screwing up the internal flags in the
> >FILE structure. I took the liberty to update newlib's setvbuf to the
> >OpenBSD version locally and I'm going to apply my patches to newl
On Mar 12 16:37, Kaz Kylheku wrote:
> On 12.03.2016 14:29, Corinna Vinschen wrote:
> >On Mar 12 20:39, Corinna Vinschen wrote:
> >>On Mar 11 16:05, Kaz Kylheku wrote:
> >>> We can reproduce the problem with just file streams using
> >>> a much simpler program:
> >>> [...]
> >>> The contents of file
On 12.03.2016 14:29, Corinna Vinschen wrote:
I do now. Basically it's setvbuf screwing up the internal flags in the
FILE structure. I took the liberty to update newlib's setvbuf to the
OpenBSD version locally and I'm going to apply my patches to newlib
soon. I'll provide a new 2.5.0 test relea
On 12.03.2016 14:29, Corinna Vinschen wrote:
On Mar 12 20:39, Corinna Vinschen wrote:
On Mar 11 16:05, Kaz Kylheku wrote:
> We can reproduce the problem with just file streams using
> a much simpler program:
>
> #include
>
> int main(void)
> {
> FILE *out = fopen("file", "w+");
> setvbuf(ou
On Mar 12 20:39, Corinna Vinschen wrote:
> On Mar 11 16:05, Kaz Kylheku wrote:
> > We can reproduce the problem with just file streams using
> > a much simpler program:
> >
> > #include
> >
> > int main(void)
> > {
> > FILE *out = fopen("file", "w+");
> > setvbuf(out, (char *) NULL, _IOLBF,
On Mar 11 16:05, Kaz Kylheku wrote:
> We can reproduce the problem with just file streams using
> a much simpler program:
>
> #include
>
> int main(void)
> {
> FILE *out = fopen("file", "w+");
> setvbuf(out, (char *) NULL, _IOLBF, 0);
> getc(out);
> clearerr(out);
> fseek(out, 0, SEEK_
On 11.03.2016 14:14, Marco Atzeri wrote:
On 11/03/2016 22:57, Kaz Kylheku wrote:
On 11.03.2016 12:08, Yaakov Selkowitz wrote:
On 2016-03-11 13:16, Kaz Kylheku wrote:
On a Cygwin installation version 1.7.33-2(0.280/5/3), I encountered
an odd issue.
This is a 15-month old release which is no
On 11/03/2016 22:57, Kaz Kylheku wrote:
On 11.03.2016 12:08, Yaakov Selkowitz wrote:
On 2016-03-11 13:16, Kaz Kylheku wrote:
On a Cygwin installation version 1.7.33-2(0.280/5/3), I encountered
an odd issue.
This is a 15-month old release which is no longer supported. Please
update to 2.4.1.
On 11.03.2016 12:08, Yaakov Selkowitz wrote:
On 2016-03-11 13:16, Kaz Kylheku wrote:
On a Cygwin installation version 1.7.33-2(0.280/5/3), I encountered an
odd issue.
This is a 15-month old release which is no longer supported. Please
update to 2.4.1.
Do you mean, "Please update to 2.4.1, i
On 2016-03-11 13:16, Kaz Kylheku wrote:
On a Cygwin installation version 1.7.33-2(0.280/5/3), I encountered an
odd issue.
This is a 15-month old release which is no longer supported. Please
update to 2.4.1.
--
Yaakov
--
Problem reports: http://cygwin.com/problems.html
FAQ:
Hi all,
On a Cygwin installation version 1.7.33-2(0.280/5/3), I encountered an
odd issue.
I wrote it up in a StackOverflow question:
http://stackoverflow.com/questions/35928828/cygwin-missing-stream-data-due-to-stdio-putc-line-buffering
This contains a repro test case.
For the benefit of no
12 matches
Mail list logo
