[Bug libstdc++/14112] Problem with Multi Threading safety in GCC 2.95.2

["lakshman_pspl at yahoo dot com" <gcc-bugzilla at gcc dot gnu dot org>]

------- Additional Comments From lakshman_pspl at yahoo dot com  2004-02-12 08:51 -------
Hi,
Thanks for the information. I cannot give you a test case for this as this is a 
race condition, and happening at high concurrency. This is not reproducible at 
will since it happens less often BUT it is happening for sure. I myself don't 
have a test case to reproduce the problem at will.

What will be more useful for me is:
===================================
1. When closing two fstreams more or less simulataneously, the application is 
crashing. Are fstream operations in gcc-2.95.2 with libstdc++ 2.10.0 multi-
thread safe or not? 
>From my posting and earlier postings, do any of you see that the crash is 
happening because of lack of thread-safety in gcc-2.95.2?

2. I have read some postings, discussions online about this. They are say if 
underlying c library is thread safe, then gcc 3.3.x is also thread-safe. I want 
to confirm it. Migrating our big application to gcc-3.3.x is a very costly 
operation for us. But once we do that, we would like not to see thread-safe 
problems in gcc-3.3.x. Thst is the reason i am asking for confirmation from gcc 
experts.

3. There are 2 postings which are very similar to my case:
a. http://gcc.gnu.org/ml/libstdc++/2001-11/msg00071.html
b. http://mail.gnu.org/archive/html/bug-gplusplus/2000-10/msg00035.html
Are these problems solved in gcc 3.3.x.? If yes, it means my problem is also 
solved.

4. Finally, If someone can say, gcc 3.3.x is thread-safe instead of saying gcc-
3.3.x is more thread-safe than gcc 2.95.2, I will be really happy to continue 
migrating from 2.95.2 to 3.3.x.

I know these are lot of questions. But your help will be really valuable for us.

Thanks a million in advance,
Lakshman.

-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14112