public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: peturr02@ru.is To: gcc-gnats@gcc.gnu.org Subject: libstdc++/9423: filebuf::pubsetbuf(0, 0) doesn't turn off buffering if called after open Date: Thu, 23 Jan 2003 18:56:00 -0000 [thread overview] Message-ID: <20030123185243.30424.qmail@sources.redhat.com> (raw) >Number: 9423 >Category: libstdc++ >Synopsis: filebuf::pubsetbuf(0, 0) doesn't turn off buffering if called after open >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Thu Jan 23 18:56:00 UTC 2003 >Closed-Date: >Last-Modified: >Originator: peturr02@ru.is >Release: gcc-3.2.1 >Organization: >Environment: Red Hat Linux 8.0 >Description: Given a filebuf fb, calling fb.pubsetbuf(0, 0) doesn't turn off buffering (as determined by fb.pptr()), if pubsetbuf is called after fb.open(). pubsetbuf(0, 0) is only guaranteed to work if called before the first I/O operation - I don't think open qualifies as an I/O operation. In any case, this is at worst implementation defined behaviour, and the documentation at http://gcc.gnu.org/onlinedocs/libstdc++/27_io/howto.html states that this should work. >How-To-Repeat: See attachment. >Fix: >Release-Note: >Audit-Trail: >Unformatted: ----gnatsweb-attachment---- Content-Type: text/plain; name="setbufbug2.cc" Content-Disposition: inline; filename="setbufbug2.cc" #include <fstream> using namespace std; class Derived_filebuf : public filebuf { public: bool is_unbuffered() const { return pptr() == NULL && epptr() == NULL; } }; int main() { Derived_filebuf dfb; dfb.open("tmp", ios_base::out); dfb.pubsetbuf(0, 0); assert(dfb.is_unbuffered()); return 0; }
next reply other threads:[~2003-01-23 18:56 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-01-23 18:56 peturr02 [this message] 2003-03-02 18:39 paolo 2003-04-14 17:03 bkoz 2003-04-15 22:46 paolo
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=20030123185243.30424.qmail@sources.redhat.com \ --to=peturr02@ru.is \ --cc=gcc-gnats@gcc.gnu.org \ /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).