|
From: Julian S. <js...@ac...> - 2009-08-12 23:46:47
|
On Thursday 13 August 2009, Nicholas Nethercote wrote: > > ================================================= > > ./valgrind-new/helgrind/tests/pth_spinlock.stderr.diff > > ================================================= > > --- pth_spinlock.stderr.exp 2009-08-13 02:12:38.000000000 +1000 > > +++ pth_spinlock.stderr.out 2009-08-13 02:23:23.000000000 +1000 > > @@ -1,2 +1,24 @@ > > Start of test. > > +Thread #x was created > > + ... > > + by 0x........: pthread_create@* (hg_intercepts.c:...) > > + by 0x........: main (pth_spinlock.c:46) > > + > > +Thread #x: Bug in libpthread: recursive write lock granted on > > mutex/wrlock which does not support recursion + at 0x........: > > pthread_spin_lock (hg_intercepts.c:...) > > + by 0x........: thread_func (pth_spinlock.c:27) > > + by 0x........: mythread_wrapper (hg_intercepts.c:...) > > + ... > Julian, do you know what is happening here? This is glibc 2.9. Looks like some scheduling-induced instability. I thought I had this working on this box, but I see now that for multiple back to back runs, sometimes it works (no errors reported) and sometimes it fails as per the above. Is on my to-fix list. J |