public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "viriketo at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/52169] New: the ifstream readsome() method does not signal any bit on eof. Date: Wed, 08 Feb 2012 10:31:00 -0000 [thread overview] Message-ID: <bug-52169-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52169 Bug #: 52169 Summary: the ifstream readsome() method does not signal any bit on eof. Classification: Unclassified Product: gcc Version: 4.6.2 Status: UNCONFIRMED Severity: normal Priority: P3 Component: libstdc++ AssignedTo: unassigned@gcc.gnu.org ReportedBy: viriketo@gmail.com Created attachment 26608 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=26608 Run it with "./c2 c2.cpp" and it will loop forever The ifstream readsome() method does not signal any bit on eof, and I think it should. Therefore, these loops loop forever: while(f && !f.eof()) { char b[5000]; size_t read = f.readsome(b, sizeof b); cerr << "Read: " << read << " bytes" << endl; ostr.write(b, read); } According to http://www.cplusplus.com/reference/iostream/istream/readsome/ : Errors are signaled by modifying the internal state flags: eofbit The get pointer is at the end of the stream buffer's internal input array when the function is called, meaning that there are no positions to be read in the internal buffer (which may or not be the end of the input sequence). This happens when rdbuf()->in_avail() would return -1 before the first character is extracted. failbit The stream was at the end of the source of characters before the function was called. badbit An error other than the above happened.
next reply other threads:[~2012-02-08 10:31 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-02-08 10:31 viriketo at gmail dot com [this message] 2012-02-08 10:40 ` [Bug libstdc++/52169] " tom at kera dot name 2012-02-08 10:46 ` tom at kera dot name 2012-02-08 10:53 ` viriketo at gmail dot com 2012-02-08 10:57 ` redi at gcc dot gnu.org
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=bug-52169-4@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@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).