-
-
Notifications
You must be signed in to change notification settings - Fork 56
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
Using the extension #124
Comments
@nimski I think you might find this comment useful: P403n1x87/austin-vscode#24 (comment) The idea is to allow Austin to run with |
Thanks very much @P403n1x87 . Following that example Austin indeed can run without sudo and I'm able to successfully create a profile with |
Ah that's weird 🤔 . I have just tried with the following in {
"version": "2.0.0",
"tasks": [
{
"type": "austin",
"label": "Test Austin tasks",
"command": [
"sudo"
],
"args": [
"python3.9",
"-c",
"from time import sleep; sleep(2)",
]
},
]
} and I've got the following flame graph Could you maybe try with the absolute path to |
That was it! It's working well now. Thatnks for your help. |
Description
Is there a way to run Austin with
sudo
on MacOS using the VS Code extension? I'm able to run Austin from the terminal directly, but when attempting to run it with sudo using the following script, I get the error messageaustin process exited with code 1
.{
"label": "pytest with austin",
"type": "austin",
"command": ["sudo"],
"args": [
"${workspaceRoot}/.venv/bin/python",
"-m",
"pytest",
"-k",
""TEST NAME""],
"problemMatcher": []
},
Expected behavior: I'd expect Austin to run the task with sudo (the only way to run it in MacOS) and pipe it to the flamegraph viz.
Actual behavior: Exits with
austin process exited with code 1
.Reproduces how often: Every time.
Versions
Version 3.3.0. MacOS 12.3 (Monterey)
Thanks for your help!
The text was updated successfully, but these errors were encountered: