public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: johnb@stl.sarov.ru
To: gcc-gnats@gcc.gnu.org
Subject: libstdc++/7276: strstreambuf (charbuf,N,charbuf) doesn`t allowed to read.
Date: Thu, 11 Jul 2002 06:36:00 -0000	[thread overview]
Message-ID: <20020711133112.4176.qmail@sources.redhat.com> (raw)


>Number:         7276
>Category:       libstdc++
>Synopsis:       strstreambuf (charbuf,N,charbuf) doesn`t allowed to read.
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Thu Jul 11 06:36:00 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator:     johnb@stl.sarov.ru
>Release:        g++3.1
>Organization:
>Environment:
RH Linux release 7.2
>Description:
I use the constructor strstreambuf (buf,n,buf) for strstreambuf object, but can`t read from it. Write operations passes OK. Only after write operation buffer  can be read. This impossibility of reading influence on strstream,istrstream objects which calls such constructor. See the simple testcase.


>How-To-Repeat:
Compile and run testcase attached with g++ 3.1.
>Fix:

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

I2luY2x1ZGUgPHN0cnN0cmVhbT4KI2luY2x1ZGUgPGlvc3RyZWFtPgoKI2RlZmluZSBJdAlzdGQ6
OmNoYXJfdHJhaXRzPGNoYXI+CgppbnQgbWFpbihpbnQsIGNoYXIgKltdKQp7CgljaGFyICpidWYg
PSBuZXcgY2hhciBbNV07CglzdGQ6OnN0cmNweSAoYnVmLCJhYmNkZWYiKTsKCglzdGQ6OnN0cnN0
cmVhbWJ1ZiBzb21lYnVmIChidWYsNSxidWYpOwoJCglpZiAoc29tZWJ1Zi5zZ2V0YygpID09IEl0
Ojp0b19pbnRfdHlwZSgnYScpKSAKCSAgIHN0ZDo6Y291dCA8PCAiUmVhZGluZyBwYXNzZWRcbiI7
CiAgICAgICAgZWxzZQoJICAgc3RkOjpjb3V0IDw8ICJSZWFkaW5nIGZhaWxlZFxuIjsKCi8qCSAg
IAoJc29tZWJ1Zi5zcHV0YygneCcpOyAKCglpZiAoc29tZWJ1Zi5zZ2V0YygpID09IEl0Ojp0b19p
bnRfdHlwZSgneCcpKSAKCSAgIHN0ZDo6Y291dCA8PCAiV3JpdGluZyBwYXNzZWQgIVxuIjsKCWVs
c2UKCSAgIHN0ZDo6Y291dCA8PCAiV3JpdGluZyBmYWlsZWQgIVxuIjsKCiovCQoKICAgZGVsZXRl
KGJ1Zik7CiAgIAogIHJldHVybiAwOwogfQoKCg==


             reply	other threads:[~2002-07-11 13:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-11  6:36 johnb [this message]
2002-11-19 12:36 bkoz

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=20020711133112.4176.qmail@sources.redhat.com \
    --to=johnb@stl.sarov.ru \
    --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).