similar to: TCP and UDP DTrace provider specifications for review

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

All, With Jon Haslam''s exciting news about the DTrace doc wiki (if you haven''t seen it yet, make your way to http://wikis.sun.com/display/DTrace), and with some of the discussion with the Apple folks, I''m wondering if the time isn''t right for something of a DTrace summit, perhaps as an unconference. The idea here would not be a DTrace user group (though that

I have added a specification of probes for the fibre channel COMSTAR port provider to the DTrace section of wikis.sun.com. The proposal may be found here: http://wikis.sun.com/display/DTrace/fibre+channel+Provider I welcome feedback regarding this proposal. Thanks, Sam

Greetings, is there a way to specify probes and other dtrace operations via command line parameters, like " BEGIN { usr_exec=$$1; usr_syscall=$$2; } syscall::usr_syscall:entry /execname == usr_exec && guard++ == 0/ { ... " [this does not work] This would make it possible to create "generic" dtrace scripts. Otherwise, some shellscript with sed-magic would

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

N_conreq:entry { self->x=1; calledaddr=(struct xaddrf *)arg3; callingaddr=(struct xaddrf *)arg4; trace(calledaddr->link_id); tracemem(calledaddr->DTE_MAC.lsap_add, 80); trace(callingaddr->link_id); tracemem(callingaddr->DTE_MAC.lsap_add, 80); } 0 -> N_conreq 255

Hi all, What is the correct way to give one non-root user the ability to use DTrace with providers running in a process by another user? Through the Web Stack project and some work by Ludovic Champenois and Nasser Nouri, we have done a bit of work to bring together parts of chime, the Web Stack Apache, Ruby and PHP providers, and stuff reused from the DTrace toolkit. It''s in

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 All, Can I get Dtrace command, which is useful for regular system administration like performance issue. Advance Thanks Muthu -- This message posted from opensolaris.org

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

I''d like to prepend TRACE_ to the macro names generated by dtrace -h. For example, change POSTGRESQL_LWLOCK_ACQUIRE(arg0, arg1) to TRACE_POSTGRESQL_LWLOCK_ACQUIRE(arg0, arg1) and still keep postgresql as the provider name. The reason for doing this is to make it clear that the macros are used for (D)tracing. In this particular case, without TRACE_, it appears like the macro is used

X.Org has adopted GNU autoconf as its build configuration mechanism, so when I integrated the dtrace probes, I checked to see if they should be built using this test, checking for the existence of a program named "dtrace" in the path: dnl Check for dtrace program (needed to build Xserver dtrace probes) AC_ARG_WITH(dtrace, AS_HELP_STRING([--with-dtrace=PATH], [Enable dtrace

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, This is not a DTrace technical question (so, please don''t flame me for it) :) This is regarding the DTrace (un)conference TShirt. I am curious to know what engine is it. Could not figure it out. Thanks and regards, Sanjeev. -- Solaris Revenue Products Engineering, India Engineering Center, Sun Microsystems India Pvt Ltd. Tel: x27521 +91 80 669 27521

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

Dtrace does work on some workstation, such as as follows, ----------------------------------------------------------- bash-3.00# dtrace -s ./mem.d `pgrep test` dtrace: script ''./mem.d'' matched 5 probes ^C bash-3.00# uname -a SunOS ftp 5.10 Generic_118833-17 sun4u sparc SUNW,Sun-Blade-100 bash-3.00# dtrace -V dtrace: Sun D 1.1

I''m getting an odd behavior while trying to trace a mysql process using the -p flag on a Sun Cluster. This fails # dtrace -n ''pid$target::*mysql_parse*:entry {}'' -p `pgrep -x mysqld` dtrace: failed to grab pid 16537: process is traced Yet this works # dtrace -n ''pid$1::*mysql_parse*:entry {}'' `pgrep -x mysqld` dtrace: description

The dtrace(1M) manpage seems to be incorrect, it states: -32 | -64 The D compiler produces programs using the native data model of the operating system kernel. You can use the isainfo -b command to determine the current operating system data model. If the -32 option is specified, dtrace forces the D compiler to compile a D

Hi all, I''m trying to run dtrace -c on a program that takes command-line arguments... is there any way to tell dtrace where its args let off and the target''s begin, or will I have to write a shell script that checks for ''--'' or some such? Thanks, Ryan -- This message posted from opensolaris.org

I''m pleased to pass along news that the Mac OS X DTrace port has been updated in 10.5.3 to fix the issue that caused timer based probes not to fire in the presence of certain untraceable applications. http://blogs.sun.com/ahl/entry/apple_updates_dtrace A big thank you to the folks at Apple for addressing the problem. Adam -- Adam Leventhal, Fishworks