|
From: Jeremy F. <je...@go...> - 2005-03-14 22:21:14
|
Christopher Gautier wrote:
>This message is about a problem I encountered with valgrind, how I
>investigated it, and how I "fixed" it. I'm not sure the "fix" is
>correct.
>
>I recently upgraded valgrind on my Debian box, and I could not
>valgrind a heavily multi-threaded project anymore (100+ threads).
>It would deadlock. strace told me that the system was regularly
>polling on a futex(FUTEX_WAIT) call.
>
>What would happen is that valgrind would run for a few seconds (so that
>most of the threads are spawned), then 2 messages like this would
>appear:
>
>
OK, that should be pretty easy to fix. Your change isn't correct, but
it isn't far off. I think the correct fix is to only look at the
arguments a particular futex operation actually uses.
J
|