-
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
Instruments can't seem to read the trace files #41
Comments
I'm going to needs macOS/Instruments versions in order to investigate this. |
I'm on MacOS Catalina 10.15.6, using Instruments version 12.4. |
Same, though I don't see the nil object error. Trace files just won't open. Instruments: Version 11.3.1 (11C504) Running |
i'm not able to reproduce on macos 10.15 with instruments 12.4. my gut instinct here is that it's something like your binary is exiting too quickly, and there's no data generated or something? I would see if you can generate a valid profile directly using the
and see if this produces a trace you can open? |
Yes, that works. I can open that trace.
|
good question, where did that file name come from? |
I assumed cargo-instruments generates it...that's the filename in |
interesting, I expect names to be in the format |
I think historically colons are also not allowed. OSX sometimes swaps them, according to a brief search. That seems to be what I'm seeing. |
interesting, this may be file system dependent? in any case I can patch to remove colons, thanks. |
So it doesn't seem to be colons. cross-posted from #47: I'd love to figure out if this is a problem with specific projects, or if it's a problem with your environment, if you have a chance to try If you don't have anything handy, something I just tested was one of the examples in piet: git checkout https://github.com/linebender/piet.git
cd piet/piet-common
cargo instruments -t time --example=mondrian --features png does this work for you? |
That example does work for me. |
@teymour-aldridge is the project that is not working for you public? |
Yeah that example works.
I don't know what kind of app this is. Mine are both services that keep running, so for me, the last thing I see is the "Profiling" line, never the "Trace file" line. Maybe because my apps don't exit. And Instruments never opens. |
oh, if your process never exits then instruments is just running forever. You can use the If you want to actually attach to the process while it is running, you're better off doing that through the GUI Instruments.app. |
Yep, which isn't super helpful, so I've been doing just that, running it from the GUI. So everything works as expected for me, then! |
@teymour-aldridge Is your application also something that never terminates, or do you think you have a different problem? |
In my case, the Here's the program:
The command:
Produces these errors: Environment:
Instruments 13.0 Thanks! |
Hi @hartshorne
I ran into the same problem. I am using Big Sur 11.6.1 (20G224) but the same Instruments version. It worked after I manually unzipped the missing file and moved it to the right place. This seems a bug in Instruments. This Stack Overflow answer explains how to do that: https://stackoverflow.com/a/67991957/2239513 |
I don't know if this is helpful for anyone, but I was somewhat surprised to find out that trying to end profiling with |
I ran into the same problem. |
I'm trying to profile some code, but whenever I run
cargo-instruments
I encounter this error:The text was updated successfully, but these errors were encountered: