search for: plockstat

Hi, I would like to know why dtrace -l |grep plockstat show plockstat28099 lines. Process with pid 28099 is a java process. Why can I not examine other processes with the plockstat provider? Is it a java startup option? Regards Hans -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.opensolaris.org/piperma...

Hello, I need help here about plockstat on X86 platform (Sun X4600 AMD) # plockstat -A -p 20034 plockstat: processing aborted: Abort due to systemic unresponsiveness # plockstat -e 5 -s 10 -A -x bufsize=100k -x aggsize=20m -p 20034 plockstat: processing aborted: Abort due to systemic unresponsiveness # ps -ef | grep 20034 algodev 20034...

Hi - I''m trying to use plockstat to help identify any mutex contention issues we may have in our c++ app. >From the docs it would appear to be a very useful tool - unfortunately in practice this doesn''t bear out purely because the stack traces produced are limited to being 39/40 characters wide. In general this means...

when check java process lock statistics, plockstat failed, please see below: # prstat -mLp 21162 PID USERNAME USR SYS TRP TFL DFL LCK SLP LAT VCX ICX SCL SIG PROCESS/LWPID 21162 7677 0.9 0.1 0.0 0.0 0.0 99 0.0 0.3 83 89 215 0 java/81 21162 7677 0.3 0.1 0.0 0.0 0.0 0.0 99 0.2 106 33 305 0 java/35 21162 7677 0.1 0.0 0.0...

Hey, Im able to reproduce a crash from plockstat everytime Im tracing a JVM pid. I do recall a problem related with this one, but not clear if this has been fixed in U3 or is it planned for U4 ? Any BugID opened for this stack trace: > ::stack libc.so.1`strlen+0x50(100003faa, ffffffff7ffff5c8, ffffffff7eca1114, ffffffff7fffec79, 0, 100003fa9)...

Hi: on a niagara platform, right after invokation of the plockstat(1M) for monitoring all events to a specific user-land process. It locks all monitored user-land processes pointer is very appreciated Thanks This message posted from opensolaris.org

Author: ahl Repository: /hg/zfs-crypto/gate Revision: 72ce7e116da4db6c063a5c3c3f1bec23ce3ca69a Log message: 6395902 use of USDT probes can cause plockstat and other scripts to fail Files: update: usr/src/lib/libdtrace/common/dt_pid.c

...that all RECV_REQ_ACT_EV sites pass the same arguments to the DTRACE_* macros that mark the probe locations, and (b) Establish the appropriate provider stability, which is done by #pragma D attributes after the provider foo { } declaration. Here is an example set of declarations from plockstat in libc: #pragma D attributes Evolving/Evolving/ISA provider plockstat provider #pragma D attributes Private/Private/Unknown provider plockstat module #pragma D attributes Private/Private/Unknown provider plockstat function #pragma D attributes Evolving/Evolving/ISA provider plockstat name #pragma...

How do I query an application to see if it supports any USDT probe points?

...sysinfo:::modload probe does not fire when using ''modload'' 6265417 schedctl-yield isn''t listed in sdt_subr.c 6272558 gcc and dtrace don''t get along 6276101 dtrace -G behaves strangely with multiple scripts 6284880 intrstat can leak dynamic variable state 6295662 plockstat needs more characters for stack addresses 6296903 invalid memory accesses clear other DTrace error bits Files: update: usr/src/cmd/dtrace/dtrace.c update: usr/src/cmd/intrstat/intrstat.c update: usr/src/cmd/plockstat/plockstat.c update: usr/src/lib/libdtrace/common/dt_link.c update: usr/src/l...

Hello, I am trying to get documentation how how this lazyloading happens when you are dealing with dtrace probes being added to user applications. In particular if it somehow avoids the overhead of registering dtrace probes when they aren''t needed, how does it know if they are needed, etc... thanks, Robert

...dtrace.c update: usr/src/cmd/fm/modules/sun4u/USII-io-diagnosis/iod_main.c update: usr/src/cmd/fm/modules/sun4u/cpumem-diagnosis/cmd_cpu.c update: usr/src/cmd/intrstat/intrstat.c update: usr/src/cmd/lockstat/lockstat.c update: usr/src/cmd/mdb/common/modules/dtrace/dtrace.c update: usr/src/cmd/plockstat/plockstat.c update: usr/src/lib/libdtrace/common/dt_aggregate.c update: usr/src/lib/libdtrace/common/dt_cc.c update: usr/src/lib/libdtrace/common/dt_consume.c update: usr/src/lib/libdtrace/common/dt_errtags.h update: usr/src/lib/libdtrace/common/dt_handle.c update: usr/src/lib/libdtrace/commo...

...9;t do that, but it would be nice to know when deadlocks occur and include a stack trace of the involved threads. What I have in mind is: 1. Use a profile provider that fires every 5 seconds or so & looks at a given process. 2. Iterate through the locks each thread is holding & use the plockstat provider to check for cycles. 3. Output the stacktraces of the related threads. Is there a script that does this already? Am I missing something obvious here? Thanks This message posted from opensolaris.org