Hey John,
Can you send me the output of that dtrace(1M) invocation with '-x debug' added
to the command-line? Thanks.
- ahl
On Tue, May 20, 2008 at 11:47:09AM -0700, John Zolnowsky x69422/408-404-5064
wrote:
> In investigating a hang in kcfd, I wanted to find the call path to
> libxml2's xmlInitParser() routine. So, under snv89, I invoked dtrace:
>
> # dtrace -n 'pid$target::xmlInitParser:entry { ustack(); }' \
> -c 'elfsign verify -v /usr/lib/security/pkcs11_kernel.so.1'
> dtrace: invalid probe specifier pid$target::xmlInitParser:entry { ustack();
> }: probe description pid2794::xmlInitParser:entry does not match any probes
> elfsign: verification of /usr/lib/security/pkcs11_kernel.so.1 passed.
> ...
>
> Specifying the libxml2.so.2 module doesn't help. Removing the function
> name altogether does result in a probe at libxml2.so.2`xmlInitParser,
> but I have to search through an exhaustive list of all function calls.
> How do I narrow my probe specification?
>
> Thanks -JZ
> _______________________________________________
> dtrace-discuss mailing list
> [email protected]
--
Adam Leventhal, Fishworks http://blogs.sun.com/ahl
_______________________________________________
dtrace-discuss mailing list
[email protected]
