-
Notifications
You must be signed in to change notification settings - Fork 34
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
Not working with Big Sur? #42
Comments
hmm, I'm really not sure what's going on here. I assume you also can't run |
Indeed, it says it's not found:
|
This link solved this problem for me. https://apple.stackexchange.com/a/336589 Now I get the following error:
I'm looking at #40 to see if I can implement that solution. |
Running into the same issue with
I'm on Catalina (10.15.7) and have the xcode command line tools installed. I also have instruments installed - could we add a command line argument for overriding the automatic detection with a user-provided value? Or maybe change the detection to check that we can run I'll try to get a PR up that works for me.. EDIT: Alright, I tried falling back to instruments and it required Xcode to be installed which is not the simple solution I was hoping for. |
I'm running Big Sur 11.6 on an M1 Air. I have /usr/bin/instruments and also 'xcrun xctrace' works. But it still tells me Instruments is not installed:
|
@GregoryTravis try |
Yes, that did it. I already had the cli tools installed (I could run gcc/clang) but I guess this updated it. Is Instruments a recent addition? |
Nope, but sometimes the path to the tools can be unset, or need to be updated after a new Xcode release? I'm not really sure of all the failure conditions, I just know this happens sometimes 🤷 |
Maybe the CLI tools are now insufficient? I'm on Monterey (12.4), and attempting to run
|
hmm, perhaps? I haven't ever not had Xcode installed. |
I'm not sure whether this is a mistake on my side or a missing feature.
I have Big Sur (11.5.1) and when trying to run some cargo-instruments it fails saying "xctrace" is missing. Indeed, I can't find that binary.
Is there something I can do to run cargo-instruments on this machine (it's an Intel machine, not M1).
The text was updated successfully, but these errors were encountered: