On Fri, Mar 26, 2010 at 04:53:57AM -0700, Matt Helsley wrote: > Yup. strace would need to be modified to use that. I tried that and it still > won't work -- I seem to recall it didn't work because strace uses pid values > obtained from the wait syscall too. To make it work we'd need to be able to > translate those pids in userspace. That's do-able from userspace if you trace > all forks descending from the pidns init task. But it's not do-able for > simple attaches. That's why I was thinking Eric's setns() might be able to > help if strace used it to enter the tracee's pid namespace whenever we need > to. > > gdb often doesn't use the same methods but has similar problems with pid > namespaces.
Hmm, is there a good reason why strace does not use the data explicitly provided by the kernel but instead second-guesses it from syscall return values? I don't know anything about ptrace, really, but I'd expect the kernel to provide the tracer with out-of-band information otherwise taken from clone/waitpid/other syscalls? Best regards, Grzegorz Nosek _______________________________________________ Containers mailing list [email protected] https://lists.linux-foundation.org/mailman/listinfo/containers _______________________________________________ Devel mailing list [email protected] https://openvz.org/mailman/listinfo/devel
