Hi,

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.

Running the same on my Nevada 81 does:

$ dtrace -n 'pid$target::xmlInitParser:entry { ustack(); }'  -c 'elfsign verify 
-v /usr/lib/security/pkcs11_kernel.so.1'
dtrace: description 'pid$target::xmlInitParser:entry ' matched 1 probe
elfsign: verification of /usr/lib/security/pkcs11_kernel.so.1 passed.
format: rsa_sha1.
signer: O=Sun Microsystems Inc, OU=Solaris Cryptographic Framework, CN=SunOS 
5.10.
signed on: 12. ledna 2008 19:54:01 CET.
dtrace: pid 14760 has exited
CPU     ID                    FUNCTION:NAME
  0  76158              xmlInitParser:entry
              libxml2.so.2`xmlInitParser
              libxml2.so.2`xmlParseDocument+0x1c
              libxml2.so.2`xmlDoRead+0x6b
              libxml2.so.2`xmlCtxtReadFile+0x55
              libkmf.so.1`kmf_get_policy+0x63
              libkmf.so.1`kmf_set_policy+0x6a
              libkmf.so.1`kmf_initialize+0xf1
              libkmf.so.1`KMF_Initialize+0x21
              libelfsign.so.1`elfcertlib_init+0x2f
              libelfsign.so.1`elfsign_begin+0xac
              elfsign`getelfobj+0x1c
              elfsign`do_verify+0x20
              elfsign`main+0x568
              elfsign`_start+0x7a

Couldn't you mistype the name ?


> 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?

You can always do '-o logfile' and then open the file in editor, where
searching for string is easy.

HTH

-- 
        Vlad

Attachment: pgpjmJsj2x0Pi.pgp
Description: PGP signature

_______________________________________________
dtrace-discuss mailing list
[email protected]

Reply via email to