Re: libstdc++/5820: EOF not handled correctly on input

Re: libstdc++/5820: EOF not handled correctly on input

[Jean-Marc Bourguet]

The following reply was made to PR libstdc++/5820; it has been noted by GNATS.

From: Jean-Marc Bourguet <jm@bourguet.org>
To: bkoz@gcc.gnu.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
	nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org
Cc:  
Subject: Re: libstdc++/5820: EOF not handled correctly on input
Date: Thu, 11 Apr 2002 14:40:15 +0200

 On Tue, Apr 09, 2002 at 09:42:21PM -0000, bkoz@gcc.gnu.org wrote:
 > Synopsis: EOF not handled correctly on input
 > 
 > Responsible-Changed-From-To: unassigned->bkoz
 > Responsible-Changed-By: bkoz
 > Responsible-Changed-When: Tue Apr  9 14:42:20 2002
 > Responsible-Changed-Why:
 >     Mine, although I think Loren's analysis is probably spot-on...
 > 
 > http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=5820
 
 Could you be more explicit about the analysis?  There is nothing related at
 the given URL and I found nothing looking at the gcc-bugs archive (but then
 I looked only for my report).
 
 Thanks,
 
 -- 
 Jean-Marc

Re: libstdc++/5820: EOF not handled correctly on input

[Jean-Marc Bourguet]

The following reply was made to PR libstdc++/5820; it has been noted by GNATS.

From: Jean-Marc Bourguet <jm@bourguet.org>
To: bkoz@gcc.gnu.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
	gcc-gnats@gcc.gnu.org
Cc:  
Subject: Re: libstdc++/5820: EOF not handled correctly on input
Date: Mon, 3 Jun 2002 22:08:42 +0200

 On Mon, May 06, 2002 at 01:28:59PM -0000, bkoz@gcc.gnu.org wrote:
 > Synopsis: EOF not handled correctly on input
 > 
 > State-Changed-From-To: feedback->closed
 > State-Changed-By: bkoz
 > State-Changed-When: Mon May  6 06:28:58 2002
 > State-Changed-Why:
 >     Fixed.
 > 
 > http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=5820
 
 I'm sorry, I had not the possibility to test the fix earlier.  I just did
 now with gcc 3.1 and the behaviour is correct.
 
 Yours,
 
 -- 
 Jean-Marc

Re: libstdc++/5820: EOF not handled correctly on input

[bkoz]

Synopsis: EOF not handled correctly on input

State-Changed-From-To: feedback->closed
State-Changed-By: bkoz
State-Changed-When: Mon May  6 06:28:58 2002
State-Changed-Why:
    Fixed.

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=5820

Re: libstdc++/5820: EOF not handled correctly on input

[bkoz]

Synopsis: EOF not handled correctly on input

State-Changed-From-To: open->feedback
State-Changed-By: bkoz
State-Changed-When: Tue Apr 30 00:26:46 2002
State-Changed-Why:
    Fixed.Please try updated sources.
    

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=5820

Re: libstdc++/5820: EOF not handled correctly on input

[Jean-Marc Bourguet]

The following reply was made to PR libstdc++/5820; it has been noted by GNATS.

From: Jean-Marc Bourguet <jm@bourguet.org>
To: Benjamin Kosnik <bkoz@redhat.com>
Cc: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org,
	gcc-gnats@gcc.gnu.org
Subject: Re: libstdc++/5820: EOF not handled correctly on input
Date: Sat, 13 Apr 2002 16:38:02 +0200

 On Thu, Apr 11, 2002 at 09:54:25AM -0700, Benjamin Kosnik wrote:
 > 
 > See this bit
 > http://gcc.gnu.org/ml/libstdc++/2002-04/msg00024.html
 
 I'm sorry, I forgot to check that mailing list.
 
 > In particular, _GLIBCPP_AVOID_FSEEK defines in 
 > config/os/gnu/bits/os_defines.h should do it. Can you try this please?
 
 It does *not* solve the problem.  In fact that make it worse: with it I've
 to type 6 CTRL-D instead of 4.
 
 Thanks.
 
 -- 
 Jean-Marc

Re: libstdc++/5820: EOF not handled correctly on input

[Benjamin Kosnik]

The following reply was made to PR libstdc++/5820; it has been noted by GNATS.

From: Benjamin Kosnik <bkoz@redhat.com>
To: Jean-Marc Bourguet <jm@bourguet.org>
Cc: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org,
        gcc-gnats@gcc.gnu.org
Subject: Re: libstdc++/5820: EOF not handled correctly on input
Date: Thu, 11 Apr 2002 09:54:25 -0700 (PDT)

 See this bit
 http://gcc.gnu.org/ml/libstdc++/2002-04/msg00024.html
 
 In particular, _GLIBCPP_AVOID_FSEEK defines in 
 config/os/gnu/bits/os_defines.h should do it. Can you try this please?
 
 -benjamin

Re: libstdc++/5820: EOF not handled correctly on input

[bkoz]

Synopsis: EOF not handled correctly on input

Responsible-Changed-From-To: unassigned->bkoz
Responsible-Changed-By: bkoz
Responsible-Changed-When: Tue Apr  9 14:42:20 2002
Responsible-Changed-Why:
    Mine, although I think Loren's analysis is probably spot-on...

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=5820

libstdc++/5820: EOF not handled correctly on input

[jm]

>Number:         5820
>Category:       libstdc++
>Synopsis:       EOF not handled correctly on input
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sun Mar 03 11:16:01 PST 2002
>Closed-Date:
>Last-Modified:
>Originator:     jm@bourguet.org
>Release:        gcc-3.0.2
>Organization:
>Environment:
Debian Linux
>Description:
On all Unix variants I've tried, programs taking their input from a
terminal consider two CTRL-D (this key can be changed with stty, but
I'll use CTRL-D) in a row or one CTRL-D just at the beginning of a
line as an end of file indication.

With the C++ library furnished with gcc 3.0.2, executing:

#include <iostream>
#include <istream>
#include <ostream>

int main()
{
   int i;
   char c;
   
   std::cout << "Enter an integer: ";
   std::cin >> i;
   if (!std::cin) {
     std::cerr << "Unexpected read problem\n";
     return 1;
   }   
   std::cout << '\n' << "std::cin.eof()=" << std::cin.eof() << '\n';
   std::cout << "The number was: " << i << '\n';
   std::cin >> c;
   if (std::cin) {
     std::cerr << "Could read " << c << " after the number!\n";
   }   
}

on a Linux box with input and output directed to a terminal, I had to
type 4 times CTRL-D after 5 to get the expected result:

Enter an integer: 5
std::cin.eof()=1
The number was: 5

If I type "5", two or three CTRL-D and "a", I get:

Enter an integer: 5a

std::cin.eof()=0
The number was: 5
Could read a after the number!
>How-To-Repeat:
See description
>Fix:

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