similar to: Finding out if DNS name is served from cache

Hi! I have another problem with Dtrace: I want to get the address of a global variable used by a process if I just know the name. It''s possible with dbx with a print &name_of_the_variable but with Dtrace? trace(`name_of_the_variable) doesn''t work... Thank you very much! Fabien -- This message posted from opensolaris.org

I want to print out arguments of float and double type, such as from sin(), cos(), etc. By trial and error, I came up following macros. union { double d64; float f32[2]; int64_t s64; int32_t s32[2]; } VALUE; #define PRINT_F32_sparc(val) \

Have you considered the mdb dcmd ::pfiles? mfe at inker:~/Code/dtrace/examples$ *pfexec mdb -k* Loading modules: [ unix genunix specfs dtrace mac cpu.generic uppc pcplusmp scsi_vhci zfs ip hook neti sockfs arp usba uhci fctl s1394 stmf stmf_sbd md lofs random idm sd crypto fcp cpc fcip smbsrv nfs ufs logindmux ptm nsmb sppp nsctl sdbc rdc sv ii ipc ] > *::ps ! grep clock-applet* R 1744

Hello Srikant - A quantization distributes the results of your aggregation into ranges ordered by a power-of-two. Presumably what you''d do in your script is capture the inclusive elapsed time of each function call in your library, then use this quantization to see how tightly-banded the times are. Perhaps there''s some blocking I/O in some of your calls, for example, in which

Hi all, So I just took Sun''s dtrace class this week and one thing that piqued my interest was the instrumenting of a process''s instructions and how to find the original instructions. (I''m looking around at resources for learning SPARC assembly to help me when using mdb for analysis, though I vaguely remember pieces from a grad school compiler theory class about 10 years

Hi all, (CC''ing dtrace-discuss as an FYI+workaround) I''m using dtrace -h to define provider probes for my application, and it wraps the resulting probe provider definitions in an #if _DTRACE_VERSION. Everything works fine for cc/CC, but gcc/g++ (gccfss v4.2.0) doesn''t seem to define it and the provider call macros expand to nothing instead. A diff shows that gcc uses

The earlier post with the Dtrace probes definition (sent on April 23) was only to solicit feedback from all prospective users of iSCSI DTrace probes. I will follow up shortly with an updated document requesting approval from the community. thanks Priya -------- Original Message -------- Subject: Dtrace provider for the COMSTAR iscsi Target Port Provider - Review Request Date: Thu, 23 Apr

Francois Dion wrote: > Le lundi 16 avril 2007 ? 13:28 -0600, Ali Bahrami a ??crit : >>> Subject: >>> Re: [dtrace-discuss] Getting the function names? >>> From: >>> Bart Smaalders <bart.smaalders at Sun.COM> >>> Date: >>> Fri, 13 Apr 2007 09:48:29 -0700 >>> To: >>> fdion at atriumwindows.com >>> >>>

I am using dtrace on a Mac OS X Leopard beta. Currently I''m tracing read operations. I''d like to get info about the process which is creating the reads, as well as information about parent processes. The least amount of information I need is pid and process name, but more would certainly be a plus! I know that in the probe entry, pid, ppid, and process name are easily

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

This is from a discussion on opensolaris-tools that is somewhat relevant for DTrace community. I wrote a simple D script (http://www.opensolaris.org/os/project/onnv/onnv_build/faster_builds/tools/dtrace/dirtrace.d) that collects data for each dmake process during the Solaris build. After that the data is post-processed by a Perl script

Hi, I am kind of new to DTrace , I have written a script to time function calls in our application library , Wanted to know how to interpret the output from quantize of the elapsed time in each function call , here is a sample Here is the entry and return function for the library that is being traced pid$1:libswduar::entry { duarEntry[probefunc] = timestamp;

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:

G''Day Folks, Well, this one was my white whale. I now have a demonstration program that uses Perl, Kstat, /proc/*/usage, /proc/*/psinfo, and DTrace. The program itself is more of a prototype, I want to get serious about it and rewrite it in C. It currently has output like, # prustat -t5 -snet 10 PID %CPU %Mem %Disk %Net COMM 90 0.00 0.09 0.00 0.00

Hi there, I''ve been using OpenSolaris for three months now, and I''ve started to get interested about to get my hands dirty with DTrace. Since I have an strong GNOME background, I would like to use it to help GNOME developers to find performance problems. Federico Mena Quintero, one of the Novell GNOME guys is one of the people that are working on GNOME performance stuff. He

G''Day Folks, I''ve just rewritten iosnoop so that uses command line arguments (I caved in and used a little Bourne shell for this - hence it''s lost it''s ".d" extension). It''s much more useful now. # iosnoop -h USAGE: iosnoop [-a|-A|-Degstv] [-d device] [-f filename] [-m mount_point] iosnoop # default output

G''Day Folks, Well, I had a weekend home in Sydney while inbetween flights and have knocked out a few programs. (I''ve been programming for 23 hours straight, so if there is something really dumb in one my scripts then please excuse me :) # socketsnoop.d UID PID DIR SIZE CMD 0 19886 W 64 ssh mars 0 19886 R 80 ssh mars 0 19915 W 0

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

The open solaris dtrace page (http://www.opensolaris.org/os/community/dtrace/) has a bad link to the DTrace Guide(http://docs.sun.com/db/doc/817-6223). This message posted from opensolaris.org

> > From: vikram b > > Date: October 22, 2009 12:31:53 AM PDT > > To: dtrace-discuss at opensolaris.org > > Subject: [dtrace-discuss] dtrace problem > > > > Hi All, > > I am running dtrace on linux !! got it working some how. > > dtrace -l shows a big list.. but many issues > > > > 1. says : failed to grab process > >