|
From: Josef W. <Jos...@gm...> - 2006-09-25 16:06:05
|
On Monday 25 September 2006 17:50, Nicholas Nethercote wrote: > On Mon, 25 Sep 2006, Josef Weidendorfer wrote: > > > I still wonder about another thing: After a fork(), usually there > > is an exec(), which starts callgrind (with --trace-children=yes) > > again using the same PID. So the callgrind run of the newly started > > binary probably overwrites profile result files of "same pid > > before exec()". > > I don't see the problem. The child will have a new PID, the parent will > have the old PID, so there shouldn't be any filename collisions. I thought that exec() only replaces the memory image of a process, but does not create a new one ?! Or does the valgrind launcher fork() itself? Josef |