Hello, On Tue, Mar 15, 2011 at 01:38:36PM +0300, Dmitry V. Levin wrote: > I've skimmed through that lengthy lkml thread to get the idea how this > ptrace interaction with job control is going to be changed. My main > user space concern is that if strace will have to *not* resume tracee > with PTRACE_SYSCALL upon each CLD_STOPPED/CLD_CONTINUED notification > when running on newer kernels, and will have to continue resuming on > older kernels, then strace needs a simple and reliable runtime method > to find out whether that particular kernel needs resuming after > receiving job control notifications.
Yes, there will be. At this point, I think it would probably be better to enable the new job control behavior only if the new attach request is used along with clone tracing behavior. So, strace will see the new behavior only when it explicitly uses the new API. Thanks. -- tejun ------------------------------------------------------------------------------ Colocation vs. Managed Hosting A question and answer guide to determining the best fit for your organization - today and in the future. http://p.sf.net/sfu/internap-sfd2d _______________________________________________ Strace-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/strace-devel
