Pyflame fails on multithreaded applications with setuid about pyflame

[eklitzke]

Thanks, this is a very good bug report. I have been working on other projects recently, but I will fix this next time I have some cycles for Pyflame. I imagine this would be a pretty small change if anyone else wants to get a PR in.

[fillest]

I get the same error without using setuid in the following case:

$ cat test.py
import time
import os

print os.getpid()
while True:
	time.sleep(1)

In one terminal: python test.py. In another sudo src/pyflame --threads -p 9699 -s 10. In the third kill 9699 (alternatively, just ctrl+c the script).

Unexpected ptrace(2) exception: waitpid() indicated a WIFSTOPPED process, but got unexpected signal 15

("signal 2" in case with ctrl+c)
Ubuntu 18, latest pyflame, Python 2.7.15rc1

[fillest]

And looks like the signals get caught only by pyflame - the script continues to run.