This is the mail archive of the glibc-bugs@sourceware.org mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug libc/1995] fprintf() + fmemopen() error (?)


------- Additional Comments From michael dot kerrisk at gmx dot net  2006-04-19 19:52 -------
Subject: Re:  fprintf() + fmemopen() error (?)

> 
> ------- Additional Comments From tschwinge at gnu dot org  2006-04-19 12:17
> ------- Subject: Re:  fprintf() + fmemopen() error (?)
> 
> On Wed, Apr 19, 2006 at 02:14:54AM -0000, michael dot kerrisk at gmx dot
> net wrote: > > Unfortunately you've been bitten by GLIBC default stream
> buffering, which > > is _IOFBF, being 'fully buffered' which is synonymous
> in the manual pages > > with 'block buffered'. > > Doh!  Got it now.  Easy
> mistake to make though.  Perhaps a word or > two in the 'info fmemopen'
> page suggesting the use of > setvbuf()/setbuf() would help?
> 
> Well, what about _you_ submitting a tiny patch to make the documentation
> more useful for you?  :-)

Sure.

Here's the text that man-pages has just acquired for fmemopen.3

[[
Attempts  to  write  more  than  size  bytes to the buffer result in an
error.  (Such errors will only be visible  when  the  stdio  buffer  is
flushed.   Disabling  buffering  with setbuf(fp, NULL) may be useful to
detect errors at the time of an output operation.)
]]

Cheers,

Michael


-- 


http://sourceware.org/bugzilla/show_bug.cgi?id=1995

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]