similar to: Dtrace starts very slowly on T5440

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

The sched provider defines the stable "lgrp" variable that is the lgroup of the current CPU. This is mostly interesting when we can compare it with the actual thread home lgroup, so I''d like to extend the lwpsinfo_t structure with the new pr_lgrp field which will be implemented using translator. This will match the addition of the pr_lgrp field to the proc(4) lwpsinfo_t

To improve the performance of scripts that manipulate zfs snapshots and the zfs snapshot service in perticular there needs to be a way to list all the snapshots for a given object and only the snapshots for that object. There are two RFEs filed that cover this: http://bugs.opensolaris.org/view_bug.do?bug_id=6352014 : ''zfs list'' should have an option to only present direct

Hi, I am tracking down a problem and would like to know how I can follow a forked process with my dtrace script, or how I can trace a dynamic library. Here is the problem. I am tracing dtlogin, and specifically I am trying to determine what error libpkcs11`<routine> is returning. It turns out dtlogin forks a lot of processes, and I believe the second forked process is the one that winds

Suppose I have a USDT probe in Firefox and that I''m trying to catch the startup with a probe like this: proc:::exec-success /execname == "firefox-bin"/ { start = timestamp; } and stop tracing when Firefox hits this USDT probe: mozilla:::main-entry { exit(0); } How do I put the running firefox-bin into "trace mode" so that my USDT probe fires? Thanks, Joel

everyone, Just out of curiosity, I did a dtrace -n ''syscall:::entry { @num[execname, probefunc] = count(); }'' and looked at the entries produced by ''rm''. I see everything that rm did, *except* the unlinkat - which is unfortunate because I want to trace which processes have deleted which files. So - does dtrace contain unlinkat as a probe for a system call?

Hi there, I am trying to diagnose a performance problem on a Sun T5120 running Solaris 10. I see general poor performance using Java and, in particular, loading classes. I have developed a simple java test that loads all of the classes in a Crystal Reports JAR file (around 7000 classes) which takes much longer on the T5120 (40 secs) than on a Core 2 Duo windows PC (5 secs). I recognise that this

HI, T5220, S10U4 + patches mdb -k > ::memstat While above is working (takes some time, ideally ::memstat -n 4 to use 4 threads could be useful) mpstat 1 shows: CPU minf mjf xcal intr ithr csw icsw migr smtx srw syscl usr sys wt idl 48 0 0 1922112 9 0 0 8 0 0 0 15254 6 94 0 0 So about 2mln xcalls per second. Let''s check with dtrace:

Hi, we are developing and operating an very critical application in the financial sector. Now our customer wants us to report performance data (roundtrip times of the messages routed). My idea is using dtrace to measure the times with the pid provider catching the timestamps on entry of the in and out functions of the processes. Now my questions ;-): 1) Is this an appropriate method to monitor

We are using following dtrace script to analyze an application. However we see different number of lwp_yield and yield calls reported depending on whether we trace mutex_lock or mutex_unlock or not. The number reported when we are not tracing mutex_lock or mutex_unlock is higher. What could be going on here and which one is the correct number. This is on S10 U2. Thanks, Rao.

Hi All, Can someone help me in getting info about specific dtrace features introduced in individual S10 updates like U1,U2,U3 etc... This message posted from opensolaris.org

Hi all, I am trying to write a D script which would print ustack() for every program in the system receiving SIGSEGV. All the stacks printed in trap()/sigtoproc() context do not have meaningful symbols. The following solves the problem to some degree but I''d much rather have a self-contained D script. dtrace -w -n ''fbt:genunix:sigtoproc:entry/arg2 == 11/ {

Hi all, I have questions about something I observed just now: 1) on AMD64, S10u1: # dtrace -n ''fbt::copystr:entry{printf ("%p\n", args[0]);}'' -c /bin/pwd dtrace: invalid probe specifier fbt::copystr:entry{printf ("%p\n", args[0]);}: in action list: index 0 is out of range for fbt::copystr:entry args[ ] but # dtrace -n ''fbt::copystr:entry{printf

Hello, According to http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=4970596 and other notes I read it appears that the ability to run dtrace programs (by having dtrace_proc and dtrace_user privileges configured inside NGZ''s) has been made available (through various projects) since build 37 of Nevada. I am not merely referring to configurable privileges alone, but to

Hi, I''m trying to use dtrace to signal threads in my app when certain events happen, and the raise() action seemed adequate -- looking at the kernel sources, it sends a signal to the currently executing thread, and a quick microbenchmark confirmed this. However, further testing showed that if lots of threads hit the event simultaneously, the signal only gets delivered once, and may also

Hello, I''m building some simple monitoring tools to watch zfs storage servers. Is this possible to run dtrace script for example 10 seconds? (Of course it is, I just trying to figure out how). Right know it has to be stopped by "CTRL-C" I''m particulary interested in scripts like iscsiio.d, iscsiwho.d from

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

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 hi, i''m trying to use the nfsv3 provider on S10U6, with the following simple script: #! /usr/sbin/dtrace -s #pragma D option quiet nfsv3:::op-read-start { printf("%s\n", args[1]->noi_curpath); } however, when running it, i get the following error: dtrace: failed to compile script ./nfs2.d: line 5: failed to grab

I read some of the previous posts on this forum, which discussed this particular problem. I tried to use the solution that those posts suggested, but I am still having a problem with my dtrace application running on a heavily loaded system. I have the following lines in my D script, #pragma D option aggsize=8m #pragma D option bufsize=16m #pragma D option dynvarsize=16m #pragma D option aggrate=0

Just adding a few more details to the previous mail so that I can avoid some trouble for you folks. 1. I have done a /execname != "dtrace"/ to avoid dtrace itself causing more syscalls to be fired. 2. I have also supressed the printing on the terminal which makes dtrace slower. And what happens is this: dtrace -qn ''syscall::read:entry /execname != "dtrace"/ {