You are correct that proc.communicate() invokes wait(), or rather
waitpid(), but "proc" here is the strace process itself, which is not
being traced, so should be irrelevant.
Perhaps I'm missing something, but I don't think that part of the man
page applies to this case: there's no *child* being traced that is being
wait()ed for. All there is is a thread, and the parent never wait()s or
joins it while strace is running, so the part of the man page you quote
doesn't seem to be relevant.
Regardless, the current behaviour seems to make it impossible for a
program to reliably call strace -f on itself, which I think is a
desirable thing to support. For debugging purposes, being able to wrap
a function call with something that starts & stops strace would be quite
handy.
I hope you don't mind me putting the status back to Unconfirmed for the
moment.
** Changed in: strace (Ubuntu)
Status: Rejected => Unconfirmed
--
strace leaves process SIGSTOPped after detaching
https://bugs.launchpad.net/bugs/103133
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
[EMAIL PROTECTED]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
