← Back to context

Comment by trumpdong

1 day ago

Or you could call ptrace_syscall (that doesn't currently exist) on your child processes that you are tracing because you'd always be tracing them by default, or get an io_uring for the child process, or...

4 comments

trumpdong

Reply
uecker  1 day ago

A ptrace_syscall would be interesting and would seem to be a full replacement for having the pid argument everywhere.

But frankly, I am not really seeing the value.

  • trumpdong  20 hours ago

    The value is not needing to change every other syscall and not needing to write new ones with a pid argument (besides which, what when you want to change it to a pidfd argument? then you add pidfd_syscall instead of duplicating every syscall again)

    • uecker  8 hours ago

      I meant the value of running syscalls in another process from the parent process in contrast to (v)forking and running them in the child directly.

      1 reply →