|
From: Patrick O. <Pat...@in...> - 2005-03-11 10:15:54
|
Hi all, 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. For that one I have filed a bug: http://bugs.kde.org/show_bug.cgi?id=101291 The test program listed there demonstrates both problems. -- Best Regards, Patrick Ohly The content of this message is my personal opinion only and although I am an employee of Intel, the statements I make here in no way represent Intel's position on the issue, nor am I authorized to speak on behalf of Intel on this matter. |
|
From: Nicholas N. <nj...@cs...> - 2005-03-11 14:19:20
|
On Fri, 11 Mar 2005, Patrick Ohly wrote: > For that one I have filed a bug: > http://bugs.kde.org/show_bug.cgi?id=101291 > The test program listed there demonstrates both > problems. Thanks for the report. Looks like Jeremy is on it. N |
|
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
|
|
From: Patrick O. <Pat...@in...> - 2005-03-14 14:47:53
|
On Fri, 2005-03-11 at 16:42 -0800, Jeremy Fitzhardinge wrote: > >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. Thanks, the problem is fixed. However, now I ran into another one, please see my other email. -- Best Regards, Patrick Ohly The content of this message is my personal opinion only and although I am an employee of Intel, the statements I make here in no way represent Intel's position on the issue, nor am I authorized to speak on behalf of Intel on this matter. |