-
Notifications
You must be signed in to change notification settings - Fork 143
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
flamegraph incompatible with macOS dtrace #75
Comments
FWIW, flamegraph 0.3.0 seems to be working fine for me on current Catalina. |
I also get the dtrace usage message on Mojave (10.14.6), with flamegraph 0.3.0. |
I was able to run on macOS (10.15), and saw a number of error messages:
however it did successfully complete:
|
@chamons What version of OSX were you running? So far, we've got two reports of it failing on Mojave, and one of success on Catalina. |
Apologies, I thought I pasted it. 10.15.6 (19G73) |
Maybe this helps someone figure it out: I can run flamegraph 0.3.1 on macOS 10.14.6, but only when I pass no arguments to the executable. |
Also happens on
|
If you are having this issue, please try my fix in #100. |
@djc Your fix seems to work for me. Thank you! |
Works for me as well. :) |
I created a new tool, which fixes this issue and supports running any target. |
When running flamegraph on version
0.2.0
, it only results indtrace
showing me it's usage message, indicating that the flamegraph tool used a wrong invocation.For reference, I use macOS Mojave (Version
10.14.6
) with the stock dtrace.The text was updated successfully, but these errors were encountered: