Bug 46365 – libstdc++ 2.96 stringstream does not work correctly

Bug 46365 - libstdc++ 2.96 stringstream does not work correctly

Summary:	libstdc++ 2.96 stringstream does not work correctly

Status:	CLOSED CURRENTRELEASE

Aliases:	None

Product:	Red Hat Linux
Classification:	Retired
Component:	libstdc++ (Show other bugs)
Sub Component:
Version:	7.1
Hardware:	i386 Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Jakub Jelinek
QA Contact:
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2001-06-27 22:24 EDT by Felipe Bertrand
Modified:	2008-05-01 11:38 EDT (History)
CC List:	1 user (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2002-12-15 10:15:31 EST
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Felipe Bertrand 2001-06-27 22:24:46 EDT

From Bugzilla Helper:
User-Agent: Mozilla/4.77 [en] (X11; U; Linux 2.4.3-12 i686; Nav)

Description of problem:
stringstream operator >> does not work when used after
operator <<. The following program does not print
"5" in g++ 2.96 with libstdc++ 2.96 (it works OK in
g++ 2.95, however):

#include <sstream>
main()
{
   stringstream ss;
   int i=0;
   ss << 5;
   ss >> i;
   cout << i <<endl;
}

How reproducible:
Always

Steps to Reproduce:
1. compile the small sample code provided
2. execute
3. the output is 0 (incorrect) intead of 5 (correct).

	

Actual Results:  The output of the compiled program is 0

Expected Results:  The output should be 5

Additional info:

Comment 1 Need Real Name 2002-05-02 11:11:07 EDT

I verified this problem also on updated Red Hat 7.0 and  
on Mandrake 8.2. 
So I guess it is a general problem of gcc 2.96 and a very nasty 
one. 
 
gcc 3.04, 3.1 and 2.95.x work fine.

Note You need to log in before you can comment on or make changes to this bug.