Re: [Valgrind-developers] New things to play with

[Jeremy F. <je...@go...>]

On Mon, 2003-08-18 at 09:32, Ashley Pittman wrote:
> This seems to work for me using a modified Redhat based 2.4 kernel. 
> I've not played with the signal stuff yet but the non-blocking syscall
> code does the trick nicely.

Thanks for the feedback.  I've been doing a number of incremental
updates since the first announcement, so I'd be interested in seeing if
you get any improvements or regressions.  What kinds of programs have
you tried it on?

> > This patch still doesn't implement clone() for application use, but it
> > should be relatively simple to add.  The main problems are 1) choosing
> > which subset to impement, 2) getting all the clone semantics correct,
> > and 3) choosing which version of clone to implement (it changed a lot
> > between 2.4 and 2.6).
> 
> I had to modify valgrind slightly to ignore the clone call before I
> could use it on my system but that's a relatively minor issue.

Ignore in what way?  Allow cloned threads to run independently of
Valgrind?

	J