[prev in list] [next in list] [prev in thread] [next in thread] 

List:       opensolaris-dtrace-discuss
Subject:    Re: [dtrace-discuss] explanation on plockstat output
From:       James Litchfield <James.Litchfield () Sun ! COM>
Date:       2009-05-11 21:49:49
Message-ID: 4A089D7D.90404 () sun ! com
[Download RAW message or body]

Some of them are statically allocated (and therefore have names that
can be extracted from CTF data) while others are dynamically
allocated - usually as part of a larger data structure.

Jim Litchfield
-------------------

Luojia Chen wrote:
> Hi,
> 
> when I'm running plockstat, I got some output for locks and caller functions as:
> 
> utex block
> 
> Count     nsec Lock                         Caller
> -------------------------------------------------------------------------------
> 131953  1473446 0x114fed408                  \
> libcmdbeng75_solsp64.so`TryLockRxMutex+0x164 116070  1623044 0x114fed408            \
> libcmdbeng75_solsp64.so`TryLockRxMutex+0x164 1974  5003636 \
>                 arserverd`nextIDinCache_lock arserverd`TryLockRxMutex+0x164
> ...
> 
> Do you know why in the output, some shows the lock name, such as: \
> 'arserverd`nextIDinCache_lock" as above, but some can't show name but only \
> address:0x114fed408 
> Thanks in advance for your info.
> 
> 
> Jenny
> 
> 
> Luojia(Jenny) Chen              
> Software Engineer                 
> ISV Engineering      
> v-mail:(510) 550-2394                                  
> SUN Microsystems
> _______________________________________________
> dtrace-discuss mailing list
> dtrace-discuss@opensolaris.org
> 
> 

_______________________________________________
dtrace-discuss mailing list
dtrace-discuss@opensolaris.org


[prev in list] [next in list] [prev in thread] [next in thread]