Ben Frederickson

I think this is a great idea - we just need support for discovering the python processes running on the system first, which will require some OS specific code. I...

Thanks for the bug report! I really need to see both the native/python stack traces at a single moment to figure this out. Can you run your program - and...

Interesting! thanks for tracking this down. It does look like the issue is with gevent hiding the ancestor stack trace, causing us to think we're not merging correctly. I think...

This looks like a bug - I think the problem is that we're getting python interpreter information from the python process when py-spy starts (including addresses etc) and those all...

@boxed There is a dev release that you can try out here: ```pip install py-spy==0.4.0.dev0``` (osx/linux only). Once you have it installed you can launch by going ```py-spy serve --...

Hmm - I don't have an aarch64 box to test on =(. The permission denied errors make me wonder though - is this related to docker? I notice in the...

I think the CI problem isn't related to the wrong remoteprocess version getting picked up - but is instead maybe related to missing unwind binaries on the travis ci box....

I've taken a pass at the CI here: I changed to use github actions (instead of travis/appveyor) and am using a raspberry pi with this instead of just cross compiling...

Hmm - I don't think it's the progbits vs nobits difference ... I just tested this out in a centos 6.9 docker container, and py-spy worked for me (and it...

This seems to be because the memory layout for debug builds of python is different. https://github.com/python/cpython/blob/9e71917e0290972f65711f75510078f799cf0b59/Include/object.h#L67-L71 : ```c #ifdef Py_TRACE_REFS /* Define pointers to support a doubly-linked list of all...