|
From: Josef W. <Jos...@gm...> - 2006-09-25 15:30:08
|
On Monday 25 September 2006 17:01, Christoph Bartoschek wrote: > Am Mittwoch, 20. September 2006 23:40 schrieb Josef Weidendorfer: > > Regarding this commit: > > Christoph, can you check it this is working for you? > > > > Seems to work fine for me. > > Is the > > REDIR: 0xFFFFFFFFFF600000 (???) redirected to 0x3802779B (???) > > message each time I use callgrind_control on the child ok? AFAIK such redirections are decided at translation time of some function. Given that everytime when the instrumentation mode is switched (e.g. by using callgrind_control -i ...) callgrind flushes the translation cache, such a redirection is redone whenever the given function is executed again. So yes, it is reasonable. So the patch seems fine. 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()". Ideas how to best solve this? Perhaps Callgrind should add an option for specifing the first sequence number to use for intermediate dumps... Josef |