Adam Leventhal wrote: > On Thu, Nov 01, 2007 at 01:58:29PM -0500, Peter Shoults wrote: > >> I think I know the answer to this, which I think is no, but want to make >> sure. Is there any way to trace any invocation of a library (and >> library routine) by any pid? I want to record all invocations of a call >> to a certain library call, no matter what pid invokes it ultimately. >> >> Please tell me there is some trickery that will allow me to do this. >> > > You can't do that today with DTrace. Of course, it's only software -- we > could implement something like that if the use case was compelling. Can > you explain what you're doing? > > Adam > > Adam,
Before I replied, I wanted to make sure I could discuss this on the opensolaris aliases. The code I am working with is Kerberos code that we have license to work with and is in the public domain, so I am cleared to go. The overall problem: Data corruption of an internal kerberos database was experienced, and analysis of existing data did not yield any conclusive root cause to the problem. Next step action plan: We wanted to develop a dtrace script that would capture the raw data that would be used to modify the internal database just before it was actually used to update the database. I have written this script, and it does dump out the record. However, it turns out that the database can be modified by three different methods, and each of these can be run many times under different pid numbers of course. The three methods are kadmin, kadmin.local and kpasswd. So, while my dtrace script did dump out exactly what we wanted, there was no way to get it to track and dump out records for multiple different pids that could be started up at any time. Hope that helps provide a good indication of what we were trying to accomplish. Peter _______________________________________________ dtrace-discuss mailing list [email protected]
