|
From: Christoph B. <bar...@or...> - 2006-09-13 09:01:32
|
Am Mittwoch, 13. September 2006 10:40 schrieb Tom Hughes: > In message <200...@or...> > > Christoph Bartoschek <bar...@or...> wrote: > > I start our program with the option --trace-children=no but callgrind > > still seems to profile the child our program starts. > > Are you actually doing an exec(), or just a fork()? > > You see trace-children is a bit badly named as it doesn't control > tracing over fork but tracing over exec, so if you fork but don't > actually exec a new program it will still be traced. > > Tom I do not have the source of the program, but with strace I see that the new child is created with clone: clone(child_stack=0, flags=CLONE_CHILD_CLEARTID|CLONE_CHILD_SETTID|SIGCHLD, child_tidptr=0x2aaaaada62d0) = 20888 And then no execve is performed because the functionality of the child is in the same programimage. Christoph |