|
From: Julian S. <js...@ac...> - 2006-08-27 14:58:22
|
On Sunday 27 August 2006 15:25, Bart Van Assche wrote: > Hello Julian, > > You asked me to look at the drd output for pth_once. Can you please be > more specific ? What I originally meant was, can you look at why drd asserted. But since that's solved now, investigating the errors from glibc is also useful. > By this time I looked up why drd complains about > _IO_stdfile_1_lock. The reason is simple: at least in glibc > 2.3.5_IO_lock_t::cnt and _IO_lock_t::owner are accessed in a > non-threadsafe way > (_IO_lock_t is a member of _IO_FILE_plus, the datatype of > stdin/stdout/stderr). [...] That's very interesting. Is it a glibc bug or did the glibc authors intend that, do you know? J |