Hi Gautam,
I am talking about a userland application which does database queries. To simplify, let's say main() calls A(). Sometimes A takes too long to return, so I want to know what parameters were passed (maybe the query is too broad or inefficient). If I run a DTrace script at this point, the pid$1::A:entry fbt provider will not be triggered and pid$1::A:return will be too late (because the problem does not exist anymore). If A() is a small function, then I could put a probe on every instruction but in this case it is complex and calls many other functions.
You could use speculations. In other words, trace every entry to A() as a speculation but only commit if the return probe fires late.
-- Peter
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ dtrace-discuss mailing list [email protected]
