Christoph Koehler
Christoph Koehler
Same, though I don't see the nil object error. Trace files just won't open. Instruments: Version 11.3.1 (11C504) Mac OSX 10.14.6 Mojave cargo-instruments 0.4.1 Running `cargo instruments -t time`
Yes, that works. I can open that trace. `app_Time-Profiler_2021-08-16T14/03/05.trace` -> Are the slashes valid characters in the file name?
I assumed cargo-instruments generates it...that's the filename in `target/instruments` when I run `cargo instruments -t time`. In your example for directly calling `instruments`, the file is (obviously) `out.trace`.
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.
Yeah that example works. ``` ❯ cargo instruments -t time --example=mondrian --features png Finished dev [unoptimized + debuginfo] target(s) in 0.24s Profiling target/debug/examples/mondrian with template 'Time Profiler' Trace file target/instruments/mondrian_Time-Profiler_2021-08-17_133758-856.trace...
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!
I'd also love to change default behavior. Rarely do I want to just checkout the commit, I most often want to switch/track.
Check out mailcow.
I just upgraded from 14 through all major versions, one by one, to 18, and everything is still working fine.
Hm seems to work for me, but I did also update to Traffic 2.