Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I’m curious if anyone (with a bit of Valgrind experience) has an idea how to tell Valgrind’s coretool that a fork in the client has occurred.
Consider the simple profiling tool lackey. When one traces instructions with lackey and the client forks, you will have two “lackeys”, one tracing the parent and the other tracing the child. However; I’m wondering if anyone has an idea how to “stop” the parent lackey at the point of the fork or shortly after.
Hope this makes sense, thoughts?
Well I figured it out shortly after but neglected this answer until now.
Valgrind has the capability of tracking system calls thus actions can be taken pre and post system call invokation. The pub_tool interface has them happily waiting to be used and instrumented.