wind64/2008: Failed to find _PyThreadState_Current symbol - won't be able to detect GIL usage

[mattp-]

trying to run against a 64bit 3.6.5 python, received the following:

[2020-10-21T21:30:50.425035100Z INFO  py_spy::python_spy] Getting version from python binary BSS
[2020-10-21T21:30:50.440637900Z INFO  py_spy::python_spy] Failed to get version from BSS section: failed to find version string
[2020-10-21T21:30:50.440637900Z INFO  py_spy::python_spy] Getting version from libpython BSS
[2020-10-21T21:30:50.440637900Z INFO  py_spy::version] Found matching version string '3.6.5 (v3.6.5:f59c0932b4, Mar 28 2018, 17:00:18) [MSC v.1900 64 bit (A'
[2020-10-21T21:30:50.440637900Z INFO  py_spy::python_spy] python version 3.6.5 detected
[2020-10-21T21:30:50.440637900Z INFO  py_spy::python_spy] Failed to get interp_head from symbols, scanning BSS section from main binary
[2020-10-21T21:30:50.440637900Z INFO  py_spy::python_spy] Failed to get interpreter from binary BSS, scanning libpythonBSS
[2020-10-21T21:30:50.549857500Z INFO  py_spy::python_spy] Found interpreter at 0x0000000000525000
[2020-10-21T21:30:50.565460300Z WARN  py_spy::python_spy] Failed to find _PyThreadState_Current symbol - won't be able to detect GIL usage
Error: Incorrect function. (os error 1)

not sure what else I can provide, but i you have any requests I'd be happy to try to fulfill. thanks!

[benfred]

What OS is this on (it looks like it might be windows but wanted to verify)? Is the version of python something I can download and try out myself?

I think the _PyThreadState_Current is just a warning - it should still work without GIL detection.

Are you running this in the 'top' mode - and if so does this work with the 'record' command instead? I'm wondering if this is related to console-rs/console#35 . If you're running in top mode - what terminal are you using?

[mattp-]

@benfred this was an internally built python3.6.5, calling dump via powershell. I think it might be just a windows 2008 issue, as I'm able to use py-spy with the same python on win2016 just fine. so i'm happy to close this and pretend i never saw it :)

[benfred]

going to close - I think this is a bug problem from the console crate I'm using, so there isn't really much I can do to fix.