Iostream deadlock...

Fons Rademakers Fons.Rademakers@cern.ch
Tue Feb 22 08:40:00 GMT 2000


Hi,

  could somebody tell me the status of the dealock problem in iostreams?
Whenever I load libpthread.so in my app I get a deadlock when calling
istream:

(gdb) where
#0  0x4098358b in __sigsuspend (set=0xbfffee54) at
../sysdeps/unix/sysv/linux/sigsuspend.c:48
#1  0x40f27211 in __pthread_lock (lock=0x868bee0, self=0x40f2d6c0) at
restart.h:32
#2  0x40f2499a in __pthread_mutex_lock (mutex=0x868bed0) at mutex.c:84
#3  0x40f26b7b in __flockfile (stream=0xbfffefac) at lockfile.c:32
#4  0x4092d3f9 in ws (ins=@0xbffff044) at ../../../libio/iostream.h:167
#5  0x4092dbd4 in istream::operator>> (this=0xbffff044, func=0x4092d3b0
<ws(istream &)>) at ../../../libio/iostream.h:222
#6  0x40190473 in TString::ReadToken (this=0xbffff074, strm=@0xbffff044) at
BASE_Stringio.cxx:119


As far as I can see the first mention on this list of this bug was in 
Oct-97 ( http://gcc.gnu.org/ml/gcc-bugs/1997-10/msg00162.html ). Any change this
will be fixed soon?

Cheers, Fons.
-- 
Org:    CERN, European Laboratory for Particle Physics.
Mail:   1211 Geneve 23, Switzerland
E-Mail: Fons.Rademakers@cern.ch              Phone: +41 22 7679248
WWW:    http://root.cern.ch/~rdm/            Fax:   +41 22 7677910


More information about the Gcc mailing list