Re: libstdc++/76: Segmentation fault on AIX on multi-threaded "Hello World"

[Benjamin Kosnik <bkoz at redhat dot com>]

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

From: Benjamin Kosnik <bkoz@redhat.com>
To: thomasdr@us.ibm.com
Cc: libstdc++-gnats@sourceware.cygnus.com
Subject: Re: libstdc++/76: Segmentation fault on AIX on multi-threaded "Hello World"
Date: Mon, 17 Jul 2000 15:52:54 -0700 (PDT)

 this bug reporting system is for libstdc++-v3, not libstdc++-v2, as you 
 reported. At this time, libstdc++-v3 on AIX is not supported.
 
 -benamin
 
 
 > >Number:         76
 > >Category:       libstdc++
 > >Synopsis:       Segmentation fault on AIX on multi-threaded "Hello World"
 > >Confidential:   no
 > >Severity:       serious
 > >Priority:       medium
 > >Responsible:    unassigned
 > >State:          open
 > >Class:          sw-bug
 > >Submitter-Id:   net
 > >Arrival-Date:   Mon Jul 17 13:37:00 PDT 2000
 > >Closed-Date:
 > >Last-Modified:
 > >Originator:     Dave Thomas
 > >Release:        unknown-1.0
 > >Organization:
 > >Environment:
 > AIX
 > >Description:
 > We get segmentation faults on AIX whenever multiple
 > threads try to write to cout at the same time.  
 > 
 > We reduced the problem to a two thread application.
 > Each application does a :
 > 
 >      cout << "Hello World" << endl;
 > 
 > The application will eventually generate a segmentation fault.
 > 
 > Running the test program under a debugger revealed that one
 > of the thread is always in the C "write" runtime function.
 > We noticed that the source file that our debugger wants to
 > bring up for the line of code of "write" generating  the
 > segmentation fault is NOT source shipped with gcc, but 
 > appears to be the "native" AIX C runtime, probably shipped
 > with xlC.
 > 
 > 1)  Is this a known problem? If so, is there a planned fix
 >     date?
 > 
 > 2)  Is it normal for the gcc C++ runtime to use the C
 >     xlC runtime library?