public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: tony.oliver@mci.co.uk
To: gcc-gnats@gcc.gnu.org
Subject: libstdc++/6746: ifstream::readsome() always returns zero
Date: Mon, 20 May 2002 10:16:00 -0000	[thread overview]
Message-ID: <20020520171306.31723.qmail@sources.redhat.com> (raw)


>Number:         6746
>Category:       libstdc++
>Synopsis:       ifstream::readsome() always returns zero
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Mon May 20 10:16:01 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator:     Tony Oliver
>Release:        gcc-3.1
>Organization:
>Environment:
sparc-sun-solaris2.8
Thread model: posix
>Description:
Calling ifstream::readsome() always yields a return value of zero (no bytes read).  No stream error flags are set.  This behaviour has been introduced in release gcc-3.1: it worked fine in gcc-3.0.4.

The problem appears to be confined to the filebuf part of ifstream, not the istream part, since (for instance) istringstream::readsome() does not suffer from this problem.

My installation of gcc-3.1 was configured with the following options (/home/to0001/ is my networked home directory):
--prefix=/home/to0001/app/gcc-3.1
--enable-languages=c,c++
--disable-shared
--verbose

Trivial test program source code attached.

Expected output (as output by gcc-3.0.4 version):

308 (308)
0 (308)

Actual output:

0 (0)
0 (0)
0 (0)
... [forever]
>How-To-Repeat:
g++ -ansi -pedantic -Wall -o gcc-test gcc-test.c++

gcc-test
>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:


             reply	other threads:[~2002-05-20 17:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-20 10:16 tony.oliver [this message]
2002-05-20 10:57 paolo
2002-05-20 13:39 paolo
2002-05-26  4:16 Paolo Carlini
2002-05-29  8:56 bkoz
2002-07-04 17:39 bkoz
2002-11-19 12:32 bkoz
2002-11-23  6:06 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=20020520171306.31723.qmail@sources.redhat.com \
    --to=tony.oliver@mci.co.uk \
    --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).