[634] in Pthreads mailing list archive
Re: Possibly bug in libpthread and C++ ?
daemon@ATHENA.MIT.EDU (Alex Fenyo (eowyn))
Tue Apr 15 06:57:52 1997
To: monty@analytikerna.se
Cc: pthreads@MIT.EDU
From: fenyo@email.enst.fr (Alex Fenyo (eowyn))
Date: 15 Apr 1997 12:36:30 +0200
In-Reply-To: Michael Widenius TcX DataKonsulter AB's message of Tue, 15 Apr 1997 11:49:44 +0200 (MET DST)
Michael Widenius TcX DataKonsulter AB <monty@analytik.analytikerna.se> writes:
> >>>>> "eowyn" == eowyn <Alex> writes:
> You can't use iostreams objects and pthreads because there is no wrapper around them.
> Other things should work with pthreads.
Why should there be a wrapper arround them ? If I lock a mutex every
time I use an iostream, there can not be any concurrent access and the
internal state of the iostream instance cannot then be corrupted.
Moreover, the iostream calls read and write to perform the low level
access, and read and write are wrapped by libpthread.
This strange behaviour doesn't occur if I use libc_r, another implementation
of multithreading (available on FreeBSD). And there is no specific wrapper
coming with libc_r.
This is why I'm not sure it's a question of wrapper.
Thanks,
Alexandre Fenyo
