Bug 80933

Summary: Use of ostringsteam causes segfault
Product: Red Hat Enterprise Linux 2.1 Reporter: Ken Kleiner <ken>
Component: gccAssignee: Jakub Jelinek <jakub>
Status: CLOSED ERRATA QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 2.1CC: tom_honermann
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard:
Fixed In Version: 2.96-118.7.2 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2003-05-14 06:03:17 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
code which seg faults when compiled and run on rh as 2.1 with updates applied none

Description Ken Kleiner 2003-01-02 15:25:08 UTC 
Description of problem:

It looks to be possibly a bug with ostringstream.  A seg fault occurs
when running compiled code(file attached).  Does not occur on 
Redhat 7.2 systems.  This started happening after the following updates
were applied:

cpp-2.96-116.7.2
gcc-2.96-116.7.2
gcc-c++-2.96-116.7.2
gcc-g77-2.96-116.7.2
gcc-objc-2.96-116.7.2
libstdc++-2.96-116.7.2
libstdc++-devel-2.96-116.7.2

Version-Release number of selected component (if applicable):
cpp-2.96-116.7.2
gcc-2.96-116.7.2
gcc-c++-2.96-116.7.2
gcc-g77-2.96-116.7.2
gcc-objc-2.96-116.7.2
libstdc++-2.96-116.7.2
libstdc++-devel-2.96-116.7.2

How reproducible:

Compile code attached and run it.

Steps to Reproduce:
1.Use ostringsteam in code.
2.Compile code.
3.Run a.out
    
Actual results:

Segmentation fault

Expected results:

return name of calling program to stdout.

Additional info:
Comment 1 Ken Kleiner 2003-01-02 15:27:03 UTC 
Created attachment 89053 [details]
code which seg faults when compiled and run on rh as 2.1 with updates applied
Comment 2 Tom Honermann 2003-05-13 23:15:40 UTC 
Hello.  My name is Tom Honermann.  I too am experiencing this problem.