Closed sihil closed 1 year ago
@sihil thanks for reporting this. What happens if you run this instead?
sudo austin -t 1s python -c "from time import sleep;sleep(4)"
Does it still fail to emit samples?
Oh no 🤦 that's working now and I can now see where the readme says Austin requires the use of sudo to work on MacOS
.
Perhaps that error message could be enhanced on macOS to aide future impatient users 😳
@sihil thank you very much for confirming and the feedback! If you have the time, perhaps you can test Austin from the devel
branch. It should already have the more informative error message pointing to the use of sudo
in this case (https://github.com/P403n1x87/austin/pull/173). It will be part of the 3.6 release, which should land in October, after Python 3.12 is released 🙏
Description
Struggling to get Austin running against pytest on MacOS due to what I am currently assuming is missing debug symbols in my python. I've reduced this to a minimal test case below.
Steps to Reproduce
austin python -c "from time import sleep;sleep(4)"
Expected behavior: Austin starts process and outputs profiling data.
Actual behavior: Austin tells me
It looks like you are trying to profile a process that is not a Python process.
Reproduces how often: 100%
Versions
austin 3.5.0 (via homebrew) macOS 13.4.1 on a 2019 MacBookPro (Intel) Python (various, all from pyenv)
Additional Information
When installing a version of python the build process seems to pull in libraries from various places so I wonder if this is the variable that is causing this to fail. This is the output from building 3.8.16:
This is an example run: