This is the mail archive of the
libstdc++-prs@sources.redhat.com
mailing list for the libstdc++ project.
libstdc++/76: Segmentation fault on AIX on multi-threaded "Hello World"
- To: libstdc++-gnats at sourceware dot cygnus dot com
- Subject: libstdc++/76: Segmentation fault on AIX on multi-threaded "Hello World"
- From: thomasdr at us dot ibm dot com
- Date: 17 Jul 2000 20:35:28 -0000
- Reply-To: thomasdr at us dot ibm dot com
- Resent-Cc: libstdc++-prs at sourceware dot cygnus dot com
- Resent-Reply-To: libstdc++-gnats@sourceware.cygnus.com, thomasdr@us.ibm.com
>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?
>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:
----gnatsweb-attachment----
Content-Type: application/octet-stream; name=" "
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename=" "