FreeBSD Port: valgrind-3.5.0_1,1
stas at FreeBSD.org
Mon Nov 9 10:39:08 UTC 2009
On Sun, 08 Nov 2009 23:34:49 +0100
Nikolaj Thygesen <nikolaj.thygesen at diamondbox.dk> mentioned:
> Valgrind still seems troubled when it comes to multithreaded
> programs. It seems pthread_self() always returns the same id no matter
> which thread calls it - possibly the id of last created thread. Running
> a simple test program under Valgrind fails whereas running it as a
> regular binary works fine.
> No matter how you twist and turn the creation of mutex'es they seem
> to always end up recursive, and don't really protect anything as thay
> can be taken by multiple threads simultaneously. They also seem to
> behave differently depending on whether they were initialized
> dynamically - as in using pthread_mutex_init() - or statically as in
> using PTHREAD_MUTEX_INITIALIZER.
I'll look into this soon.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 833 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20091109/2b6ca860/attachment.pgp
More information about the freebsd-ports