On Feb 12, 2009, at 07:55, Greg Troxel wrote:
Does that sound sensible; have I missed anything?
Also run tests on other than Linux, with as many different OS
threading
implementations as possible. For all systems, set the threading
libraries to the most restrictive settings, specifically
Hello,
Neil Jerram n...@ossau.uklinux.net writes:
(Is something like this actually _ever_ a problem? If locks are
always _acquired_ in the right order, how can the order of _releasing_
ever cause a problem?)
It can't be a problem, AFAIUI. I don't think Helgrind check the
releasing order,
Hello,
Ken Raeburn raeb...@raeburn.org writes:
As helgrind and NetBSD's pthread checking code work by instrumenting
the executable and watching progress, I'd suggest also trying out
static analysis tools if anyone has them handy. I see guile is
already listed with Coverity's open-source
