|
From: Jeremy F. <je...@go...> - 2005-03-12 00:42:06
|
Patrick Ohly wrote:
>FYI, valgrind 2.2.0's pthread implementation seems to have
>a problem with pthread_atfork(): it only calls the given
>child function in the first forked process, but not
>in following ones.
>
>This is probably irrelevant given the fact that 2.4.0 won't
>implement pthread calls itself any more. However, with
>2.4.0 rc2 I ran into another problem where creating
>threads in a forked process would lead to a valgrind
>assertion.
>
This should be fixed in CVS now. I'll probably put out rc3 later today,
depending on whether anything else serious turns up.
J
|