public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: peturr02@ru.is
To: gcc-gnats@gcc.gnu.org
Subject: libstdc++/9761: filebuf::pbackfail discards previously put back characters
Date: Wed, 19 Feb 2003 17:16:00 -0000	[thread overview]
Message-ID: <20030219171235.17799.qmail@sources.redhat.com> (raw)


>Number:         9761
>Category:       libstdc++
>Synopsis:       filebuf::pbackfail discards previously put back characters
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Wed Feb 19 17:16:01 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator:     peturr02@ru.is
>Release:        gcc-3.2.1
>Organization:
>Environment:
Red Hat Linux 8.0
>Description:
If filebuf::sputbackc is called twice in a row, the result of the first sputbackc is lost. It would be better for the second sputbackc to fail than to corrupt the stream. Even better would be to support up to gptr() - eback() put backs.
>How-To-Repeat:
See attachment.
>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:
----gnatsweb-attachment----
Content-Type: text/plain; name="sputbackcbug3.cc"
Content-Disposition: inline; filename="sputbackcbug3.cc"

#include <fstream>

int main()
{
	using namespace std;

	filebuf fbuf;
	fbuf.open("sputbackcbug3.cc", ios_base::in);

	fbuf.sbumpc();
	fbuf.sbumpc();
	
	if (fbuf.sputbackc('a') == EOF)
		return 0;
	if (fbuf.sputbackc('b') == EOF)
		return 0;

	assert(fbuf.sbumpc() == 'b');
	assert(fbuf.sbumpc() == 'a');

	return 0;
}


             reply	other threads:[~2003-02-19 17:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-19 17:16 peturr02 [this message]
2003-02-22 16:24 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=20030219171235.17799.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: link
Be 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).