This appears to be fixed in Ubuntu 10.10 (and perhaps earlier). The
script completes normally and immediately for me now:
$ python sigstop-demo.py
done
** Changed in: strace (Ubuntu)
Status: Confirmed = Fix Released
--
strace leaves process SIGSTOPped after detaching
** Changed in: strace (Debian)
Status: Unknown = 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
** Changed in: strace (Ubuntu)
Importance: Undecided = Medium
Status: Unconfirmed = Confirmed
--
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
** Bug watch added: Debian Bug tracker #424706
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=424706
** Also affects: strace (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=424706
Importance: Unknown
Status: Unknown
--
strace leaves process SIGSTOPped after
wait() doesn't have meaning for separate threads; only for processes.
Additionally, it is not possible to run strace, except as a separate
(child) process. And, while proc does /represent/ an interface to the
child, it's still the parent that is doing the wait()ing, upon its child
(which is the
The man page talks about wait()ing for a *traced* child. That's not the
case here. The parent is wait()ing for strace itself, which is
definitely not a traced child.
In fact, if I comment out the proc.communicate() line, so no wait()
happens, the bug still occurs. So wait() is definitely a red
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
This doesn't seem to be a bug. From strace(1), -f option:
If the parent process decides to wait(2) for a child
that is currently being traced, it is suspended
until an appropriate child process either terminates
or
** Attachment added: sigstop-demo.py
http://librarian.launchpad.net/7148040/sigstop-demo.py
--
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
