similar to: Dtrace & thread deadlock detection

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) libc.so.1`snprintf+0x88(ffffffff7ffff8f0, 0,

Author: bmc Repository: /hg/zfs-crypto/gate Revision: 213bfe03af413cdf71c523fb076aaa65a6306a7e Log message: 6256581 System got a hang or a panic with dtrace+kmdb 6264573 unanchored dtrace_getpcstack is rather imprecise toward function end 6289517 dtrace doesn''t like fd_intr anymore 6291378 dtrace helpers can interfere with the use of kmdb 6295554 dtrace doesn''t report

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 1 2 07:00:54 ? 86:17

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 that I''m not seeing ~75% of each stack symbol and

> I have a code that has several probes with the same probename. When I define the probe to use a translator and then try to match for all the occurances of the probename in a D script I get the following error: > > dtrace: invalid probe specifier mpi__test$target:::RECV_REQ_ACT_EV { printf("%d %d", args[0]->bar, args[0]->baz); }: in action list: args[ ] may not be

Author: ahl Repository: /hg/zfs-crypto/gate Revision: a2677fc0a5fb6895ed56fc4698646ece44978a48 Log message: 4970475 There should be a stackdepth equivalent for userland 5084954 value of dip can be incorrect in autovec 6181505 dtrace sysinfo:::modload probe does not fire when using ''modload'' 6265417 schedctl-yield isn''t listed in sdt_subr.c 6272558 gcc and dtrace

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:

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 0.0 0.0 100 0.0 0.1 79 6 85 0 java/59

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

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

Hi All, I have a java application (Multithreaded architecture) which goes in for a DEADLOCK(hang state) after 4 days. Previously, when my application had a DEADLOCK i used a JProbe Profiler to find the solution. JProbe profiler fails to detect the present DEADLOCK as my application goes for a hang only after 4 days and JProbe cannot sustain running for 4 long days and fails(VM closes) with

Dear R-users, a new R package has been released named orddom. This package provides ordinal estimates as alternatives to independent or paired group mean comparisons, especially for Cliff?s delta statistics. It provides basic parameters for various robust tests of stochastic equality with ordinally scaled variables. For two sets of data, ordinal comparison estimates are calculated such as -

Dear R-users, a new R package has been released named orddom. This package provides ordinal estimates as alternatives to independent or paired group mean comparisons, especially for Cliff?s delta statistics. It provides basic parameters for various robust tests of stochastic equality with ordinally scaled variables. For two sets of data, ordinal comparison estimates are calculated such as -

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

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

To remember all dtrace actions, aggregations and variables is a headache, even worse, they are not include in dtrace(1M) now. So here is a chance to have a CLI RFE - to have something like "dtrace --actions", which will list all actions, like this page: http://developers.sun.com/solaris/articles/dtrace_quickref/dtrace_functions.html "dtrace --aggregations", lists all

I have a number of systems running solaris10 and i see the package and binary for dtrace installed however whenever we try to run anything we get this error dtrace: failed to initialize dtrace: DTrace device not available on system the only system in which i dont have this error is the development server that has the full solaris 10 install while others are minimized, do i need additional

The open solaris dtrace page (http://www.opensolaris.org/os/community/dtrace/) has a bad link to the DTrace Guide(http://docs.sun.com/db/doc/817-6223). This message posted from opensolaris.org

For those who may have missed the news, the DTrace movers and shakers have moved over to a new mailing list; you can sign up at http://dtrace.org/blogs/mailing-list/ And there will be a conference dedicated to DTrace on April 3rd in San Francisco, more information here: http://wiki.smartos.org/display/DOC/dtrace.conf -- best regards, Deirdr? Straughan SmartOS Community Manager Joyent cell

Just to let people know what my big picture is, I''m trying to write a script that will let me run a program, and name a progeny of that program that I want to debug. My script should find the first occurrence of that progeny, and run it until it finishes initializing the runtime linker, but stop it before it runs any shared library startup routines. (Failing that, I''d be okay