similar to: User process probe. Stack depth and flow indent skips and mismatches.

If I use a simple dtrace script such as this: fbt::somefunc:entry{self->trace=1;} fbt::somefunc:return{self->trace=0;} fbt:::entry{} fbt:::return{printf("%lx", arg1);} then it will descend to whatever depth is necessary If I want to limit it to say 3 functions deep, how can I do that? The quick answer I want to use is to do "self->depth++" on each entry and then

Hi all, I remember at OSCON 2005 there was talk of adding DTrace probes to PHP (in fact, I have a photo of Bryan and Wes working on it!). Did they ever get into the upstream branch, ''cause I don''t recall seeing a --enable-dtrace (or similar) configuration option when I recently built PHP 5.2.1. If not, is there an ETA? TIA, -- Rich Teer, SCSA, SCNA, SCSECA, OpenSolaris CAB

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

Hi: I''m running Indiana (OpenSolaris developer preview) under parallels in OS X 10.5.1. I can consistently get Solaris to hang. Doing a dtrace -n pid\$target::malloc:entry''{@=count()}'' -c ls will consistently hang Solaris. Basically doing anything with PID provider with the -c option seems to hangs Solaris. Only way to recover is to stop and start Parallels desktop.

Hi, I am adding DTrace probes within NFS v3 client. In my current implementation, I use some tsd_*() functions and kmem_zalloc() function. These functions might be heavy and affect the performance. I want to call this function only when DTrace is running or the DTrace probes are enable. So is there a way to check DTrace is running or DTrace probe is enabled? Regards, Danhua

Hy! I receive an nxge driver messages on console: Aug 18 11:08:42 [hostname] nxge: NOTICE: nxge_ipp_eccue_valid_check: rd_ptr = XXX wr_ptr = YYY I find the bug description/correction at sun web page, and i know i can ignore it. I thinking about how can i delete from console only these messages (here is my first version, what is not (so) elegant): #!/usr/sbin/dtrace -qs #pragma D option

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

Hi: I got OpenSolaris 2008.05 running as dom0 under VmWare fusion on my MacBook pro. Using the instructions from Dipleep''s blog http://blogs.sun.com/dkumar/entry/how_to_create_domu_in Everything seems okay except the networking. When booting OpenSolaris (without dom0) the pcn0 interface works just fine but when booting Solaris xVM version them pcn0 does not work (ie) I get failures

I use a lot of tabs and Firefox runs very slowly. I would like to figure out which tabs are eating up resources (cpu, memory, etc). Will the Mozilla dtrace framework be any help with this? -- This message posted from opensolaris.org

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

Hi, I have mentioned before that we have added some sdt dtrace probes in SAX, our APL interpreter. Encouraged by Angelo and Jignesh, I have created a small document (5 pages) describing our experience with it, together with some problems we have encountered and some scripts we use for pretty-printing dtrace outputs. The said document can be found at

Hi, I''m trying to trace a jvm using the hotspot provider. I''ve enabled the flag ExtendedDTraceProbes for the running process: /opt/j2sdk-1.6.0.16/bin/amd64/jinfo -flag +ExtendedDTraceProbes 25255 But I didn''t get the expected result: dtrace -n ''hostspot$1::: {} '' 25255 dtrace: invalid probe specifier hostspot$1::: {} : probe description

Hi, I have used dtrace in the past for diagnosing IO/filesystem related issues. So I am a bit familiar with dtrace scripts Now I want to diagnose performance problems in the java area. May be memory leak etc. The hotspot provider is not present. How can I get them? Does someone have any further advice? regards Hans -- This message posted from opensolaris.org

Hi all, There''s a dead thread about this back at http://forums.sun.com/thread.jspa?threadID=5075157, but it would be really nice to have support for if/else control flow in actions. Reasons: 1. The ternary operator ?: is already there (though it doesn''t let you do anything with side effects) 2. The user can already write arbitrary and expensive non-cacheable predicates if

Hello, I''m using the below dtrace script to capture the flow and times of kernel functions, from an ioctl() call. After an entry into restorectx(), the trace of startimestamp - vtimestamp makes a dramatic jump downwards. Here''s the snippet showing the jump... 6 -> di_checkmem 8 220176600 6 <- di_checkmem

[Perhaps someone could rename this list to dtrace-matt-problems-discuss?] If I run this script against my binary (which contains a USDT probe called ''concurrentq-latency''): ::: / probename == "concurrentq-latency" / { printf("[%s]:[%s]:[%s]\n", probeprov, probefunc, probename); } I get this output: dtrace: script ''testq.d'' matched 46056

Maybe someone can share that script with me? Full problem i''m trying to investigate - my S10u7 get I\O error when accessing LUN on EMC cx480, but only if LUN created on raid6 raid group. When I create one on raid5 or raid10 everything goes fine. -- ____________ Voropaev Pavel -------------- next part -------------- An HTML attachment was scrubbed... URL:

hi, I am trying to find out the avg cpu time spent in each of my user methods (exclusive of other methods invoked by a method). Hence the following snippet failed miserably: ----------------------- pid$target:a.out::entry { time[probefunc] = timestamp;} pid$target:a.out::return { @spent[probefunc] = avg(timestamp - time[probefunc]);} END { printa(@spent);}

I recently did a backport of a couple of networking bug fixes from s10x_u4_b6 to s10x_u3_b10. I patched just /platform/i86pc/kernel/unix and /platform/i86pc/kernel/amd64/unix in my existing u3 OS image and I''m seeing this dtrace problem when running any dtrace script: NODE hcb101 ~ $ ./tcpstat.sh dtrace: failed to compile script /dev/fd/10: "/usr/lib/dtrace/procfs.d", line

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