|
From: Nicholas N. <nj...@cs...> - 2008-03-10 20:23:52
|
On Sun, 9 Mar 2008, Josef Weidendorfer wrote: >>> It is even more difficult if the child sometimes afterwards does an exec, >>> and VG does follow the new executable. Then, the new log file started after >>> the exec will overwrite the file already written to between fork and exec. >> >> Is that a problem? It might be a little inefficient (although the new flag >> --child-silent-after-fork can help), but I don't see how it would cause a >> correctness problem? > > Lost lines in the log file for sure can be a problem? As the child after > fork has the same PID as the new Valgrind process after exec in this child, > the log file name will be the same. Or am I missing something here? I see. I guess if a fork follows an exec, in practice it will be almost immediate so anything lost would be unimportant? But in general, yes, there's the potential for lost information. Nick |