-
Notifications
You must be signed in to change notification settings - Fork 435
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error: Failed to find a python interpreter in the .data section #1
Comments
Thanks for the bug report! This is really helpful. It seems like you found two different problems:
Also If you see the symbol files for python36 and it still doesn’t work, can you try enabling logging and rerunning?
I’m hoping to fix the code to not require symbol files on windows pretty soon - the OSX and Linux versions both work without symbols, and it shouldn’t be too hard to get this going for windows. This library is still super early in development - I’ve only really put it up here to get some early feedback (and haven’t posted it anywhere public yet =). I’m still working through some of the issues, but I am hoping to have it ready for wider release in the next week or so. Thanks again, and let me know if you find any other issues! |
The fix for working without symbols on windows turned out to be pretty easy actually: 6809f59 . I'm hoping this last commit will fix the issues you were seeing |
Thanks for the quick reply, and fix! Giving this a try next.
I came across the project on DuckDuckGo, searching for "sampling profiler python"; yours was the first result. :) |
I think it's ready for general use now - I've fixed this issue (and a bunch of others with the system python on OSX, homebrew installs etc). Thanks for giving this a go! |
It works! :) |
Hi @benfred,
Loving the goals for this project, but understand it's a little early.
Running this on Windows 10, Python 3.6 x64, profiling another instance of the same version I get this.
Likely a separate problem, but profiling a Python 2.7 x64 instance yields this.
The Python instances were merely started, with nothing much going on.
Any way I can work around this?
The text was updated successfully, but these errors were encountered: