|
From: Jeff D. <jd...@ad...> - 2004-08-04 14:12:00
|
On Wed, Aug 04, 2004 at 08:52:19AM +0100, Tom Hughes wrote: > I don't see how a patch that small can have made clone work for you in > any version - at the very least you would need a change to vg_syscall.c > to stop it trapping the clone and complaining about it or you would > never actually reach VG_(do_syscall). There may have been more - this was the only bit that I spotted in my old email. In any case, that patch was the guts of the clone support. > But how did you cope with the fact that valgrind doesn't protect it's > internal data structures in any way? You would have all sorts of > problems with two threads trying to access the same data. Despite its use of clone, UML is essentially single-threaded. The child thread goes and does something, and the parent waits for it. There is a window between the clone and wait where both could be executing at the same time, and trashing valgrind data, but I never saw that happen. Jeff |