public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: marc-oliver.gewaltig@hre-ftr.f.rd.honda.co.jp
To: gcc-gnats@gcc.gnu.org
Subject: libstdc++/8399: sync_with_stdio(false) breaks unformatted input
Date: Wed, 30 Oct 2002 02:26:00 -0000	[thread overview]
Message-ID: <20021030101703.2063.qmail@sources.redhat.com> (raw)


>Number:         8399
>Category:       libstdc++
>Synopsis:       sync_with_stdio(false) breaks unformatted input
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Wed Oct 30 02:26:01 PST 2002
>Closed-Date:
>Last-Modified:
>Originator:     marc-oliver.gewaltig@hre-ftr.f.rd.honda.co.jp
>Release:        gcc 3.1, gcc 3.2
>Organization:
>Environment:
Solaris 8, Suse Linux 8.0, and probably all others
>Description:
Unformatted input breaks if synchronisation with stdio
is set to false:
istream members
char get()
get(char &)
read(char *, size_t)
will only return on EOF and SIGINT
>How-To-Repeat:
Compile and start the program.
1. the prompt will appear once and get will
   never return. Same applies to other flavours of get
   and read. I did not test getline though.
2.  If sync_with_stdio(false) is removed, the program
   works as expected and shows a prompt after each <RETURN>
>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:
----gnatsweb-attachment----
Content-Type: application/octet-stream; name="get-test.cpp"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="get-test.cpp"

I2luY2x1ZGUgPGNhc3NlcnQ+CiNpbmNsdWRlIDxpb3N0cmVhbT4KCmludCBtYWluKCkKewogIHN0
ZDo6aW9zOjpzeW5jX3dpdGhfc3RkaW8oZmFsc2UpOwoKICBjaGFyIGM7CiAgc3RkOjppc3RyZWFt
ICppbj0mc3RkOjpjaW47CgogIGRvCiAgICB7CgogICAgICBhc3NlcnQoaW4tPmdvb2QoKSk7CiAg
ICAgIGFzc2VydCghaW4tPmZhaWwoKSk7CiAgICAgIGFzc2VydCghIGluLT5lb2YoKSk7CgogICAg
ICBzdGQ6OmNlcnIgPDwgImM9ICI7CiAgICAgIGluLT5nZXQoYyk7CiAgICAgIHN0ZDo6Y2VyciA8
PCBjIDw8IHN0ZDo6ZW5kbDsKCiAgICAgIGFzc2VydChpbi0+Z29vZCgpKTsKICAgICAgYXNzZXJ0
KCFpbi0+ZmFpbCgpKTsKICAgICAgYXNzZXJ0KCEgaW4tPmVvZigpKTsKCQogICAgfXdoaWxlIChj
ICE9ICdxJyk7CiAgcmV0dXJuIDA7Cn0K


             reply	other threads:[~2002-10-30 10:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-30  2:26 marc-oliver.gewaltig [this message]
2002-11-03 16:09 paolo
2002-11-04  4:53 paolo
2002-11-04  4:59 paolo
2002-11-10 10:46 Paolo Carlini
2002-11-20  1:36 paolo
2002-11-21  6:51 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=20021030101703.2063.qmail@sources.redhat.com \
    --to=marc-oliver.gewaltig@hre-ftr.f.rd.honda.co.jp \
    --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).