|
From: Frank L. <fra...@go...> - 2009-11-06 15:30:14
|
2009/11/6 Jeff Johnson <n3...@ma...>: > > On Nov 6, 2009, at 9:55 AM, Frank Lahm wrote: >> >> ==3960== Error: can not open cache simulation output file >> `/home/frank/callgrind.out.3473' >> > > The simplest hack-o-round is to create the file > before invoking callgrind, and ensure that it has > the permissions that the child requires to write the file. > > Use --callgrind-out-file to pass in the file to use. > > Here's is the silly wrapper I use with callgrind because > I can never remember the details: > > hth It might, but as far as I understand you workaround, the child will still write to the same file as the parent?! I can achieve the same easily in my situation, because after I start the main process and before any child forks I can easily chmod/chown the file so that the child can write to it. I've tried that once, and indeed the client wrote its dump there once it exited. But: as soon as I also quit the parent, the parent wrote it's dump to the file, overwriting the stuff from the child. Afaik the processes ought to write to different files, right? Thanks! -Frank |