|
From: Dan K. <da...@ke...> - 2003-07-01 09:20:58
|
http://www.openoffice.org/issues/show_bug.cgi?id=16270 Valgrind caught OpenOffice unlocking a mutex with a different thread than created it... tsk. Any chance this is a false positive? It'd be pretty cool if Valgrind was right here; this would explain some strange problems I've seen reported in OpenOffice. - Dan -- Dan Kegel http://www.kegel.com http://counter.li.org/cgi-bin/runscript/display-person.cgi?user=78045 |
|
From: Nicholas N. <nj...@ca...> - 2003-07-01 10:00:47
|
On Tue, 1 Jul 2003, Dan Kegel wrote: > http://www.openoffice.org/issues/show_bug.cgi?id=16270 > Valgrind caught OpenOffice unlocking a mutex > with a different thread than created it... tsk. > > Any chance this is a false positive? It'd be pretty cool > if Valgrind was right here; this would explain some > strange problems I've seen reported in OpenOffice. Well, there's always a chance it's a bug in Valgrind... but tracking which thread locks/unlocks a mutex isn't very hard, ie. it's not, AFAIK, a dark corner of Valgrind that is difficult to get right. N |
|
From: Jeremy F. <je...@go...> - 2003-07-02 07:51:08
|
On Tue, 2003-07-01 at 02:03, Dan Kegel wrote: > http://www.openoffice.org/issues/show_bug.cgi?id=16270 > Valgrind caught OpenOffice unlocking a mutex > with a different thread than created it... tsk. > > Any chance this is a false positive? It'd be pretty cool > if Valgrind was right here; this would explain some > strange problems I've seen reported in OpenOffice. Valgrind keeps that kind of mutex metadata in the mutex_t itself, so it could get a false positive if what actually happened was that the mutex was trashed. So something bad happened. J |