> Comments in source code show that real parent will get ECHILD while its
> children are ptraced. So I think maybe some early kernel does not do this
> well. The default kernel in RHEL 3.9 seems to work well about this issue
> while I doubt that not all 2.4 kernels are fine.
RHEL3 is not really 2.
> + /* In occasion of using PTRACE_O_TRACECLONE, we won't see the
The comment format used in strace is:
/*
* Comment.
*/
> + * we keep the same logic with that option and dont't trace it.
Typo there in "don't".
Thanks,
That seems fine to me, though I have no idea what motivated it.
Thanks,
Roland
--
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shif
On Fri, Sep 17, 2010 at 09:57:54AM +0300, Tommi Rantala wrote:
> Add support for RT clock IDs found in Linux, POSIX, SUS et al.:
>- CLOCK_PROCESS_CPUTIME_ID
>- CLOCK_THREAD_CPUTIME_ID
>- CLOCK_MONOTONIC_RAW
>- CLOCK_REALTIME_COARSE
>- CLOCK_MONOTONIC_COARSE
>
> * time.c: array
Sent on 2010-9-10 16:31, Roland McGrath wrote:
>> Moreover, if I got all right, in old kernels such as 2.4 series,
>> wait call will lost its children who are ptraced. I guess that's
>> why strace have function internal_wait. But in 2.6 series kernels,
>> I think wait call will block if its childre
