This is the mail archive of the libstdc++@gcc.gnu.org mailing list for the libstdc++ project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Thread safety of cout

From: Benjamin Kosnik <bkoz at redhat dot com>
To: Dan Evison <devison at pacificit dot co dot nz>
Cc: pcarlini at suse dot de, libstdc++ at gcc dot gnu dot org
Date: Fri, 8 Oct 2004 11:49:18 -0500
Subject: Re: Thread safety of cout
Organization: Red Hat / Chicago
References: <047501c4ac87$2fcb1fa0$0c01a8c0@atlantic><20041007214128.GA28512@tofu.dreamhost.com><4165D497.4040806@suse.de><20041008015225.GC10582@tofu.dreamhost.com><41664B76.6030801@suse.de><20041008130343.GE10582@tofu.dreamhost.com><4166937C.6050306@suse.de><066c01c4ad44$21ee6730$0c01a8c0@atlantic>

Dan, unless we can get a reproducable test case, most of this discussion
will be conjecture. Sorry.

Personally, I would like to get to the bottom of this.

You might also add a bugzilla  feature request to do something like
this: http://www.roguewave.com/support/docs/sourcepro/stdlibug/44-1.html
in libstdc++.

best,
-benjamin

Follow-Ups:
- Re: Thread safety of cout
  - From: Dan Evison

References:
- Thread safety of cout
  - From: Dan Evison
- Re: Thread safety of cout
  - From: Nathan Myers
- Re: Thread safety of cout
  - From: Paolo Carlini
- Re: Thread safety of cout
  - From: Nathan Myers
- Re: Thread safety of cout
  - From: Paolo Carlini
- Re: Thread safety of cout
  - From: Nathan Myers
- Re: Thread safety of cout
  - From: Paolo Carlini
- Re: Thread safety of cout
  - From: Dan Evison

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]