public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: salvador@inti.gov.ar
To: gcc-gnats@gcc.gnu.org
Cc: pavenis@lanet.lv
Subject: libstdc++/4419: ifstream::get(buffer,len) stops reading when an empty line appears.
Date: Fri, 28 Sep 2001 15:06:00 -0000	[thread overview]
Message-ID: <20010928220311.29701.qmail@sourceware.cygnus.com> (raw)

>Number:         4419
>Category:       libstdc++
>Synopsis:       ifstream::get(buffer,len) stops reading when an empty line appears.
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Fri Sep 28 15:06:01 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator:     libstdc++ streams
>Release:        libstdc++-3.x
>Organization:
>Environment:
i586-pc-msdosdjgpp      gcc-3.0.1 release
i586-pc-msdosdjgpp      gcc-3.1 20010927 (experimental)
i686-pc-linux-gnu       gcc-3.0.2 20010927 (prerelease)
>Description:
When reading a text file from an input stream using the get 
member you can't read all the file if it contains an empty
line (one with \n).
The stream stops reading lines at rhis point.
Here is the complete explanation I reported by mail:
Hi All!

  GCC 3.0 changed too much things in the C++ classes to follow the new
standard (is that ISO C++ 1998?).
  I was "fighting" to support it in the TV library. Thanks to Andris and
other
people I got the library compiled. But while testing the examples I found
a really strange behavior.
  I don't know if that is a bug and in this case if that's djgpp specific.
So I need help from somebody with:

a) Access to another systems with gcc 3.x (not djgpp)
b) Knowledge about the new streams.

  It looks like a bug and as it is for lines that only contains EOL (\r\n)
could
be related to djgpp's \r\n to \n traslation. The following code compiled
with
gcc 2.95.x can read a complete file name meassuring the length of each
line. The same code compiled with 3.0.1 will stop reading in the first empty

line and from this point will enter in an endless loop. Note that EOF is not

reached nor indicated with gcc 3.

Here is the stripped code (the original loads the text in memory):

#include <fstream.h>

const int maxLineLength=200;

int main(void)
{
 ifstream fileToView("test.txt");
 char line[maxLineLength+1];
 int len=0;
 while(!fileToView.eof())
   {
    fileToView.get(line, sizeof line);
    char c;
    fileToView.get(c);      // grab trailing newline
    printf("%d (%d)\n",strlen(line),c);
    // Sanity stop
    if (++len==20) return 1;
   }
 printf("EOF: %d\n",fileToView.eof());
 return 0;
}

Here is what you can use for `test.txt' to feed the example:

<--------
First Line
Another Line

The above is empty

<---------

Output from gcc 2.95.x compiled code:

10 (10)
12 (10)
0 (10)
18 (10)
0 (10)
EOF: 1

Output from gcc 3.0.1 compiled code:

10 (10)
12 (10)
0 (10)
0 (10)
....

SET

>How-To-Repeat:
#include <fstream.h>

const int maxLineLength=200;

int main(void)
{
 ifstream fileToView("test.txt");
 char line[maxLineLength+1];
 int len=0;
 while(!fileToView.eof())
   {
    fileToView.get(line, sizeof line);
    char c;
    fileToView.get(c);      // grab trailing newline
    printf("%d (%d)\n",strlen(line),c);
    // Sanity stop
    if (++len==20) return 1;
   }
 printf("EOF: %d\n",fileToView.eof());
 return 0;
}

/*
Use it to feed the program (test.txt):

<--------
First Line
Another Line

The above is empty

<---------
*/
>Fix:

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


             reply	other threads:[~2001-09-28 15:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-28 15:06 salvador [this message]
2001-12-08  2:42 paolo
2001-12-08  2:46 paolo
2001-12-10  4:46 salvador
2002-03-11 13:35 pme

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=20010928220311.29701.qmail@sourceware.cygnus.com \
    --to=salvador@inti.gov.ar \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=pavenis@lanet.lv \
    /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).