similar to: Truning on pid$target probes hangs Solaris

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

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

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 Folks, I''m trying to use DTrace to understand some complex code using the user process probe. Things are basically not matching up. When I use a variable to track depth, sometimes it jumps. Similarly, the flow indent seems off. I read another post saying that this is caused by missing return statements in functions.

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

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

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, 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

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

G''Day Folks, I''ve finally typed up my classic DTrace demo, which I use to introduce people to DTrace (I delivered this at SOSUG#1), http://www.brendangregg.com/DTrace/dtracevstruss.html Here I create a fault and show the difficulty in analysing it using previous tools. Then I compare the impact of analysing the problem using both DTrace and truss. DTrace wins (a lot!).

I am running a very simple multithreaded program (TestThread.C) which calls gethostbyname_r in several threads. My analysis of this program with both truss and DTrace suggest that is has a small leak. However, if I alter the program to have many more threads and run for a lot longer it never runs out of memory and does not carry on growing. Can anybody explain what I am missing in my analysis or

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 all, I am installing a zone onto two different V445s running S10U4 and the zones are taking hours to install (about 1000 packages), that is, the problem is identical on both systems. A bit of trussing and dtracing has shown that the pkginstalls being run by the zoneadm install are making door_call calls to nscd that are taking very long, so far observed to be 5 to 40 seconds, but always in

How do I find out why df -k is taking soo long to respond only sometimes? -- Asif Iqbal PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing?

I have a number of systems running solaris10 and i see the package and binary for dtrace installed however whenever we try to run anything we get this error dtrace: failed to initialize dtrace: DTrace device not available on system the only system in which i dont have this error is the development server that has the full solaris 10 install while others are minimized, do i need additional

while trying to use the USDT made available to us in Postgresql database I have problems enabling them. On my database server I ran 1024+ PG processes (1024 clients). The server is a 8 core T2000 @1000MHz. 32GB. 7 storage arrays. Solaris 10 Update 4. Home compiled PG 8.3 beta 1 (optimized binary for T1 chip) with DTrace probes enabled. When running without enabling the probes I have approx 25%

Hi all... I''ve just got my hands on a Solaris 10 box for the first time. I''ve heard wonderous things about dtrace, so the first command I type is dtrace -l which disappointingly does nothing at all. It just hangs, and neither Ctrl-D, Ctrl-C or kill -9 from another shell will do anything to kill it. The box is: SunOS t2000 5.10 Generic_118822-25 sun4v sparc SUNW,Sun-Fire-T200

OK, so this may be a little off-topic, but here goes: The reason I switched to OpenSolaris was primarily to take advantage of ZFS''s features when storing my digital imaging collection. I switched from a pretty stock Linux setup, but it left me at one disadvantage. I had been using inotify under Linux to trigger a series of Ruby scripts that would do all the basic ingestion/setup for