similar to: Measuring cpu migrations

G''Day Folks, I''ve found another use of dtrace, this makes your console keyboard sound like a typewriter. http://www.brendangregg.com/DTrace/typewriter-0.70.tar.gz I''ve only tested it on an UltraSPARC 5 and a Pentium laptop so far, more to follow. Ok, sorry, not actually a practical use of DTrace. :) Enjoy! Brendan [Sydney, Australia]

Dear dtrace Experts, I have seen some dtrace utilities like opensnoop and execsnoop etc. My interest is to write a simple script that can snoop the files which uses the 3 syscalls like open,create,unlink. I have gone through dtrace oneliners that can do the same : dtrace -n ''syscall::open*:entry { printf("%s %s",execname,copyinstr(arg0));}'' dtrace -n

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

I have been doing some profiling using the profile provider. I have a command that runs more slowly on the T1000 than it does on prior systems and I am trying to find out why. Using the profile provider at 1000 hz, and aggregating on the ustack output, I find that the same function appears at the top of the stack on both platforms, but on each there are specific instruction locations within

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

I''m interested in monitoring the amount of stack used by a multi-threaded program. I assume ''stackdepth'' built-in would be useful...but not sure. Been through demo''s, ToolKit, and internals..but it''s just not clicking for me yet. Not sure how to measure start/end of stack size dynamically...Anyone know how to break this down? This message posted from

is there a way to place regular expressions on predicates like ~ in awk such that /execname ~ prog/ matches all executables with the ''prog'' substring? thanks. This message posted from opensolaris.org

i''m using the following probe to calculate how many bytes are being written by tcp write calls, by process and total: fbt:ip:tcp_output:entry { this->tcpout_size = msgdsize(args[1]); @tcpout_size[execname] = sum(this->tcpout_size); @tcpout_size["TOTAL_TCP_OUT"] = sum(this->tcpout_size); } I run this probe for N seconds. I suppose that if i get the

Rather than failing to compile on platforms which lack POLLRDHUP such as FreeBSD, simply fallback to the old method of sleeping. This leaves the porting suggestions as a comment in case someone wants to implement a better solution for particular platforms. --- server/public.c | 38 ++++++++++++++++++++++++-------------- 1 file changed, 24 insertions(+), 14 deletions(-) diff --git

Hi, Is there a way to print out full path name of execname when the following probe is touched? proc:genunix:exec_common:exec-success Thanks. ************************************************ * C P Lin, Common Technology Project Lead. * * Sun Microsystems Inc. * * E-Mail: c.lin at sun.com * * Address: 4150 Network Circle,

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"/ {

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

Hi I have a process which reads a socket using recvfrom. After sometime, for no apparent reason, recvfrom exits with an EINTR causing the sender to barf too. Basically the socket on which these processes were communicating no longer exists. On writing a dtrace, I could determine that a signal was received at that socket causing the EINTR. I do not know of way to see who sent the signal (which

Hi, I have a system based on a Supermicro X8DTH-i motherboard and a Xeon E5506 CPU. It was previously running Debian lenny with xen-hypervisor-3.2-1-amd64 (3.2.1-2) / linux-image-2.6.26-2-xen-amd64 (2.6.26-29) without incident. I upgraded it to Debian squeeze, with xen-hypervisor-4.0-amd64 (4.0.1-4) / linux-image-2.6.32-5-xen-amd64 (2.6.32-45) and now it does not complete a boot of the dom0

Hi All, One of the customer is seeing the following error messages. He is using a S10U1 system with all latest patches. Dtrace script is attached. I am not seeing these error messages on S10U2 system. What could be the problem? Thanks, Gangadhar. ------------------------------------------------------------------------ rroberto at njengsunu60-2:~$ dtrace -AFs /lib/svc/share/kcfd.d dtrace:

From: Martin Peres <martin.peres at labri.fr> --- nvkm/subdev/pwr/fuc/kernel.fuc | 13 +++++++++++++ nvkm/subdev/pwr/fuc/nv108.fuc.h | 25 +++++++++++-------------- nvkm/subdev/pwr/fuc/nva3.fuc.h | 23 ++++++++++------------- nvkm/subdev/pwr/fuc/nvc0.fuc.h | 23 ++++++++++------------- nvkm/subdev/pwr/fuc/nvd0.fuc.h | 23 ++++++++++------------- 5 files changed, 54 insertions(+), 53

struct timespec64 has unused bits in the tv_nsec field that can be used for other purposes. In future patches, we're going to change how the inode->i_ctime is accessed in certain inodes in order to make use of them. In order to do that safely though, we'll need to eradicate raw accesses of the inode->i_ctime field from the kernel. Add new accessor functions for the ctime that we can

Strange problem on a desktop, 64 bit, SXDE3. ] ./jpg1.d dtrace: failed to compile script ./jpg1.d: "/usr/lib/dtrace/iscsi.d", line 94: syntax error near "uiscsiproto_t" Doesn''t matter what script. Even classic oneliners such as: ] dtrace -n ''syscall::open*:entry { printf("%s % s",execname,copyinstr(arg0)); }'' bomb in this way... dtrace:

There are a couple of problems with filters trying to sleep. First, when it is time to shut down nbdkit, we wait until all pending transactions have had a chance to wind down. But consider what happens if one or more of those pending transactions are blocked in a sleep. POSIX says nanosleep is interrupted with EINTR if that thread handles a signal, but wiring up signal masks just to ensure a

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