strace leaves process SIGSTOPped after detaching
Bug #103133 reported by
Andrew Bennetts
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
strace (Debian) |
New
|
Unknown
|
|||
strace (Ubuntu) |
Fix Released
|
Medium
|
Unassigned |
Bug Description
Binary package hint: strace
The attached python script starts a thread, attaches strace -f to itself, and sends SIGINT to strace to detach it. The process is then left stopped:
$ python sigstop-demo.py
[1]+ Stopped python sigstop-demo.py
$ fg
python sigstop-demo.py
done
$
If the thread is not started, the process isn't stopped by detaching strace. Similarly, if "-f" is not passed to strace, this does not occur.
This was discovered by a debug hook in bzr. There are reports this problem doesn't happen in dapper.
Changed in strace: | |
importance: | Undecided → Medium |
status: | Unconfirmed → Confirmed |
Changed in strace: | |
status: | Unknown → Unconfirmed |
To post a comment you must log in.
This doesn't seem to be a bug. From strace(1), -f option:
of course, if that child happens to be strace itself, the "until" bit probably ceases to apply.
I'm guessing the call to proc.communicate() involves wait()ing.
(Closing bug for now; if further information arises that suggests that this may still be a bug, please feel free to reopen.)