-
Notifications
You must be signed in to change notification settings - Fork 2
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
Pid with Systrace #5
Comments
nevermind, looks like TraceOutput contains Pid so simply calling .iter() on it should get what i need. Still having trouble joining multiple crossbeam_channels into one. Is there any chance that hstrace will support child processes in the future? |
Hi! This repo was more of a PoC/WIP, so not being actively developed. If I remember correctly, https://github.com/blaind/hstrace/blob/master/src/trace/hstrace_impl.rs#L200 comment was added for future performance improvements where each thread could be traced in separate thread. Forks are already detected. Added an example, check out https://github.com/blaind/hstrace/blob/master/examples/05_trace_child.rs Output (notice the increasing pid after clone):
|
Thanks! that example helps a lot. I don't have a lot of time at the moment, but really like the premise of the project and would like to help move it out of PoC if you have a list of missing features of things that need work. |
Hey, I'm looking into using hstrace for a utility im working on but strugling tracing both parent and child processes. It seems like coupling pid with syscall in the crossbeam_chanel as a touple would keep things clearer when collecting calls from parent and child processes. You could simply forward each child into a central channel or chain iterators into a single match.
Is there an easier way to do this?
The text was updated successfully, but these errors were encountered: