|
From: Tom H. <to...@co...> - 2006-09-13 12:35:51
|
In message <115...@sp...>
Dennis Lubert <pla...@pr...> wrote:
> Am Mittwoch, den 13.09.2006, 10:13 +0100 schrieb Tom Hughes:
>
>> On recent linux systems fork is actually done with clone so you do
>> have the situation I described.
>>
>> Unfortunately --trace-children is not going to help you.
>>
>> The problem is that valgrind can't really untangle itself from an
>> existing process, so it is only on an exec (when the process image
>> in memory is completely replace) that we can remove ourselves.
>
> Can't V fork() itself and then exec the program that its running? Or
> something like that?
If the client program didn't mind losing all the state it had in
memory then yes, it could. I rather suspect it will mind though.
Don't forget that a fork creates an exact clone of the process at
that point in time, complete with any data structures it has built
in dynamically allocated memory, any file descriptors it has open
and so on.
Tom
--
Tom Hughes (to...@co...)
http://www.compton.nu/
|