|
From: Josef W. <Jos...@gm...> - 2006-09-25 16:44:41
|
On Monday 25 September 2006 18:13, Nicholas Nethercote wrote: > The parent (PID 1) forks, creating the child (PID 2). After the fork, the newly created process (PID 2) can be requested to do an intermediate dump, either by callgrind_control (which works now with r6082), or by a client request resulting in a dump file in the namespace of PID 2. As this is the first intermediate dump for this PID, this is "callgrind.out.2.1". > The child immediately > exec()s, replacing its memory image with the new program, but keeping the > old PID (2). Yes. When callgrind is started for the child (PID2), the first intermediate dump with the new executable writes into existing "callgrind.out.2.1" because the dump counter (here the ".1" at end) will have been reset. Perhaps, the user never is interested in what happens between a fork() and a following exec(). When he is, the result could become overwritten. As example: it could be interesting to see what the VG launcher is doing. Or am I missing something here? Josef |