-
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
stdout #4
Comments
As far as I can tell, the instruments cli that we call swallows stdout from the child process, and there's no documented way to change this behaviour. The easiest workaround I can think of is to redirect stdout to a file for profiling; you could use a custom replacement of |
understood |
It's possible to capture the stdout from any PID with: capture() {
sudo dtrace -p "$1" -qn '
syscall::write*:entry
/pid == $target && arg0 == 1/ {
printf("%s", copyinstr(arg1, arg2));
}
'
}
# capture 1234 If I find the PID for |
When running with cargo instruments I can't see any output on the screen, is there a way to enable stdout?
The text was updated successfully, but these errors were encountered: