public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rsa at us dot ibm dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sources.redhat.com Subject: [Bug libc/1995] fprintf() + fmemopen() error (?) Date: Wed, 19 Apr 2006 20:05:00 -0000 [thread overview] Message-ID: <20060419200522.4548.qmail@sourceware.org> (raw) In-Reply-To: <20051208133403.1995.michael.kerrisk@gmx.net> ------- Additional Comments From rsa at us dot ibm dot com 2006-04-19 20:05 ------- Hi Michael, In my tests I also found that setting stream buffering to the size of buf works just as well as no-buffering and is probably a better method because it reduces turnaround, albeit slightly, i.e. setbuffer(fp, buf, sizeof(buf)); I actually sent a patch to libc-alpha that got lost in the ether somewhere (probably sitting in limbo on an ibm relay server again) that calls _IO_setbuffer() on the _IO_FILE * stream pointer in fmemopen() after the _IO_fopencookie() call in case it was deemed acceptable to change the buffering implicitly. I'll resend for comment tomorrow if the patch doesn't show up. I suggest mentioning setbuffer(fp, buf, sizeof(buf)) in the man page as the recommended method for getting around the problem. I believe the libc info page needs to be updated as well. -- 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.
next prev parent reply other threads:[~2006-04-19 20:05 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-12-08 13:34 [Bug libc/1995] New: " michael dot kerrisk at gmx dot net 2006-03-31 18:56 ` [Bug libc/1995] " rsa at us dot ibm dot com 2006-04-11 22:49 ` rsa at us dot ibm dot com 2006-04-12 22:20 ` rsa at us dot ibm dot com 2006-04-19 2:14 ` michael dot kerrisk at gmx dot net 2006-04-19 12:18 ` tschwinge at gnu dot org 2006-04-19 19:52 ` michael dot kerrisk at gmx dot net 2006-04-19 20:05 ` rsa at us dot ibm dot com [this message] 2006-04-19 21:00 ` michael dot kerrisk at gmx dot net 2006-04-19 21:41 ` rsa at us dot ibm dot com 2006-04-19 23:24 ` michael dot kerrisk at gmx dot net 2006-04-20 15:35 ` rsa at us dot ibm dot com 2006-04-20 19:33 ` michael dot kerrisk at gmx dot net 2006-04-21 13:03 ` rsa at us dot ibm dot com 2006-04-23 17:03 ` drepper at redhat dot com 2006-04-24 15:20 ` rsa at us dot ibm dot com [not found] <bug-1995-131@http.sourceware.org/bugzilla/> 2012-04-28 2:31 ` mtk.manpages at gmail dot com
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=20060419200522.4548.qmail@sourceware.org \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sources.redhat.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: linkBe 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).