Open walles opened 3 years ago
I believe that instruments itself consumes stdin
and stderr
; you can verify this by running instruments directly and seeing if there's any way to get your binary's output? Assuming this is the case I don't know how to work around this. :(
I didn't get it working.
This I think should have worked, but it didn't:
xcrun xctrace record --template "Time Profiler" --target-stdin - --target-stdout - --launch -- target/debug/riff
What I did as a workaround BTW was:
riff
riff
finished, press the stop button in the Instruments UIThen scroll down to riff
in the Instruments UI and see what happened.
you should consider opening a radar with apple (or whatever the new version of radar is) in which case send me the number and I'll file a dupe.
I want to profile this command line:
How can I do that using
cargo instruments
?Riff is a filter that reads data from
stdin
and prints it tostdout
.If I just start
riff
usingcargo instruments
, ptop says thatriff
'sstdin
andstdout
are both connected toinstruments
, which is not what I want.How do I tell
cargo instruments
how to set upstdin
andstdout
for the profiled binary?