Skip to content
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

fix #31: mention macOS status explicitely #170

Merged
merged 1 commit into from
Nov 11, 2021
Merged

fix #31: mention macOS status explicitely #170

merged 1 commit into from
Nov 11, 2021

Conversation

masklinn
Copy link
Contributor

@masklinn masklinn commented Nov 8, 2021

Disabling System Integrity Protection only seems necessary to
trace system utilities: binaries living in /System, /usr (except
/usr/local), /bin, /sbin, /var, and preinstalled applications.

Therefore tracing a rust utility probably should not conflict with
SIP, but it still requires running a superuser.

Disabling System Integrity Protection only seems necessary to
trace *system utilities*: binaries living in `/System`, `/usr` (except
`/usr/local`), `/bin`, `/sbin`, `/var`, and preinstalled applications.

Therefore tracing a rust utility probably should not conflict with
SIP, but it still requires running a superuser.
@masklinn
Copy link
Contributor Author

masklinn commented Nov 8, 2021

Note: did this on a rather outdated macOS 10.11 and it works fine (running cargo flamegraph --root is how I hit #168 — and worked around it), however if someone has access to a macOS 11 or 12 machine to make sure that'd be nice.

Given how recent the latest comments on #31 are maybe @capnfabs or @rsqv were / are running recent versions?

@fenhl
Copy link

fenhl commented Nov 11, 2021

I can confirm that these instructions work on macOS Monterey 12.0.1 with System Integrity Protection enabled.

@djc
Copy link
Contributor

djc commented Nov 11, 2021

@fenhl thanks for testing!

@djc djc merged commit 243380a into flamegraph-rs:main Nov 11, 2021
@masklinn masklinn deleted the macos-doc-support branch November 11, 2021 15:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants