similar to: CPC provider - input welcome

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);}

Hi, Finally, the long promised CPU performance counter provider has arrived into Nevada build 109! For those that need an injection of excitement at the start of the week, you can check out some usage examples on my blog: http://blogs.sun.com/jonh/entry/finally_dtrace_meets_the_cpu Also, you can find a new section for the provider in the DTrace docs:

Hi Max/DTrace list, > At any rate, without the -C, I can''t use #include <sys/stream.h>. > Without the #include <sys/stream.h>, I can''t use the M_DATA. > As it is, I get the following: > > # ./strrput.d 0xd595a6c0 <-- this is a vnode for a socket > ftp is using (not important here) > dtrace: failed to compile script ./strrput.d: line 7: >

I have found that pid provider can not create memcpy:return probe for 64bit process on snv_110. For example, the pid is 10603, I will have following output for dtrace command: #dtrace -n pid10603:libc.so.1:memcpy:return dtrace: invalid probe specifier pid10603:libc.so.1:memcpy:return: probe description pid10603:libc.so.1:memcpy:return does not match any probes This just

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:

OK, I''ve been fritzing around with something I noticed last night, thinking that I understood what was going on, but now it''s getting confusing again. A system that has been running for a couple of months had a hole in the probe ID list near the end in the middle of the fbt probes. And then a couple of syscall probes were stuck in the hole. It looked like this: ... 40311

Tracers, Good news! The Solaris Dynamic Tracing Guide has entered the participation age at last and has been converted into wiki format. The new and shiny guide can be found at: http://wikis.sun.com/display/DTrace/Documentation The guide has fallen behind with developments in DTrace since it was first released and needs some revising and some bug fixing as well. However, now that it''s

DTraceToolkit has a dtrace script (Proc/pidpersec.d) that refers to a variable mpid as below profile:::tick-1sec { printf("%-22Y %8d %6d\n", walltimestamp, `mpid, pids); pids = 0; } Where is `mpid getting picked from (it isn''t declared anywhere else)? What does the character ` in `mpid signify? I do not see any reference to this variable in the dtrace

My leaky memory says we moved entry-point into some form of debug record in the standard libraries, circa Solaris 8/9. Before that, my group maintained text files that listed all the entry-points and their parameters for libraries like libc.so, so that we could print out parameter values in apptrace(8). There''s a (small) chance the records are complete enough that dtrace could use the

This came up as an RFE during the conference (I believe it''s been logged as "4012008: brendan() action needed for DTrace Toolkit".) As everyone here is aware, DTrace is not quite as user friendly as it could be. For the uninitiated, it can be confusing to run a DTrace script and not see the expected output. Brendan Gregg has addressed this in the DTrace Toolkit[1] by

Hi Bryan, > Does that sit well with everyone? Seems fine to me. Just revisiting one of Dragan''s points, though (sorry if I missed the answer) - is there a reason for making this global (via a #pragma) rather than, say, simply providing two functions which print in the different orders? e.g. printa() for sort by sample, printak() for sort by key. My reason for wanting to do both in

Hello all, I have been taking basic steps with DTrace and subscribed today to this list. I have written a simple DTrace script to trace all the function entry/exit from a given function: #pragma D option flowindent pid$1::*mysql_select*:entry { self -> start = vtimestamp ; } pid$1::*mysql_select*:return /self -> start/ { self -> start =0 ; } pid$1:::entry, pid$1:::return

I see Intel has released a new tool. Oh, it requires some patches to the kernel to record latency times. Good thing people don''t mind patching their kernels, eh? So who can write the equivalent latencytop.d the fastest? ;-) http://www.latencytop.org/ -- cburgess at qnx.com

G''Day All, I''m putting together a PSARC case to begin integration of the DTrace network providers. I''ve drawn up a rough plan which splits this project into over a dozen smaller steps, as documented on the network provider page: http://www.opensolaris.org/os/community/dtrace/NetworkProvider#Plan Below is a draft PSARC document for task 1, IP provider send/receive

G''Day Folks, While I have a few minutes online (which is rare at the moment - travel), let me post about a couple of new scripts. I''ve just uploaded them to http://www.brendangregg.com/dtrace.html. They are to profile user-level functions and libaries; and kernel-level functions and modules. They sample, rather than trace (which can be both good and bad). Here is hotuser

Hi , I have posted DTrace script to snoop tcp traffic and also provided a wrapper script for it to filter out unwanted traffic. http://blogs.sun.com/roller/comments/raviswam/Weblog/tcp_snoop_using_dtrace Please let me know if you have any feedback/comments on this. Thanks Ravi

Is there any work on keeping DTraceTools up to date with the latest snv builds. These scripts are pretty useful and help get a novice dtrace user like me doing useful work quickly. Specifically the tcp stack tools like tcptop and tcpsnoop don''t work with later OpenSolaris builds. Thanks, Gary -- This message posted from opensolaris.org

Is it possible to use DTrace to display the number of arguments and their types for userland or kernel functions that are not explicitly instrumented or documented by their authors? We''re talking about functions provided by Veritas VxVM/VxFS and the like, and for example, we might want to try tracing I/Os from App => VxFS => VxVM => ssd driver to see where I/Os get aggregated or

As noted on my blog and at http://www.opensolaris.org/os/community/dtrace/shells/ I''ve made available a DTrace provider for the Bourne shell. Before anyone starts yelling at me for not starting with another shell, read the blog I made explaining why we started with shell (link on the community page referenced above). For /bin/sh, I''ve put up something akin to a chapter in

DTrace folks, I''m pleased to introduce a potential new DTrace-sponsored project: the Erlang DTrace provider. To be good OpenSolaris citizens, we want to put the formation of this officially sponsored project to a vote -- as outlined in the OpenSolaris Constitution -- so here are the details for the new Project, as prepared by the Project Team: Name : Erlang DTrace Integration