1Canf4N
1Canf4N
> It seems that the function doesn't cope with process comms that have ) in them. Not a very common case for Python processes, but I suppose no reason not...
hi, @Jongy Thanks for your suggestion, but using the `--nonblocking` flag is not enough for what I want to get. If this is a bug, do you have any suggestions...
> A workaround I can suggest is to add basic timeout to the logic. If we fail to lock all threads in, say, 500us * Nthreads, py-spy could bail on...
By the way, I have another simple error scenario here. Below are the contents of `/proc/{pid}/stat` for two processes. > 1981866 (python3) S 1981743 1981866 1981743 0 -1 1077936384 34709484...
> I might be able to try it out later today, will write here if so. Thank you so much for your time～ > PTRACE_SEIZE does not stop the process...
When py-spy run with `py-spy record --pid {pid} --native -r 97 -d 10 -f raw -o xxx.txt`, I try to printing the stack, as below Thread 3 (LWP 805052): #0...