search for: fbt

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 fbt cpuid cpuid_detach entry 40312 fbt cpuid cpuid_detach return 40313 fbt cpuid...

Hi all, I have questions about something I observed just now: 1) on AMD64, S10u1: # dtrace -n ''fbt::copystr:entry{printf ("%p\n", args[0]);}'' -c /bin/pwd dtrace: invalid probe specifier fbt::copystr:entry{printf ("%p\n", args[0]);}: in action list: index 0 is out of range for fbt::copystr:entry args[ ] but # dtrace -n ''fbt::copystr:entry{printf ("%p...

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 &quo...

I''m using a fbt probe where I get a system call id as an argument, how do I look up the name of it? At the moment I''m post-processing the output using /etc/name/to_sysnum but that doesn''t feel right :) cheers, /Martin -- This message posted from opensolaris.org

what is differenct between syscall::write:entry fbt::write:entry are the two probe fires at the same place. -- This message posted from opensolaris.org

Whilst trying out some D to get an insight into what is the most common reason for a given function to return, I have bumped into an error I don''t understand. The first take on what I was trying to do was: # dtrace -n ''fbt:ip:ip_input:return{@home[arg0] = count();}'' and all was well. The next step was: # dtrace -n ''fbt:ip::return{@home[strjoin(probefunc,(string)arg0)] = count();}'' but the output was not quite so friendly: dtrace: description ''fbt:ip::return'' matched 16...

Tried to start up tcptop_snv on snv87 x86 and got <i>dtrace: failed to compile script /dev/fd/11: line 168: conn_tcp is not a member of struct conn_s</i> Line 288 has this line: <i>this->tcpp = (tcp_t *)this->connp->conn_tcp;</i> which, after looking at line 168 of <a

Is there a list anywhere of the DTrace FBT provider calls for each version of Solaris since the Nevada build that hosed the DTrace Toolkit. I have no issue with rewriting what I need, but I am hoping to stave off having to look at all the source code to find everything. I know there is a new provider under development, but I need to be ab...

Hiya, I''m trying to track down some throughput latency that our customer seems to be attributing to our product, I can''t see what he''s talking about, but I want to try and get some deeper granularity than I might get with something like smokeping, and maybe even see if its down to something tunable on our end. I''ve been looking for some examples on how

Hi All: In Solaris Dtrace User Guide, page 218, it says, "Functions that do not create a stack frame on x86 systems cannot be instrumented by FBT." Then what are these functions? What characteristics do they have? Regards TJ

...at only takes two arguments but you grab size of write via arg3? i would appreciate any hints on how to accomplish this task, and an explanation of how the args work if i''m missing something Thanks James Dickens information relied on: from socketsize.d /* ** Process Socket Write */ fbt:sockfs:so_update_attrs:entry /arg1 == 1/ { /* fetch details */ this->size = arg3; cmd = (string)curpsinfo->pr_psargs; /* store details */ @Size[pid,cmd] = quantize(this->size); } from src/src/uts/common/fs/sockfs/socksubr.c void so_update_attrs(st...

I''m curious to know what files are being used from a NFS server perspective. I''m unable to trace the client because it is in the boot phase. Looking at the io provider, I believe it does not allow you to look at what files are being requested. That would lead me to the fbt provider. Does anyone know what fbt provides the file handle for NFS client request on the NFS server. Thanks Dave

Hi. I would like to print out a field of a vnode, but the argument to the function is of type vnode_t **. If I set "this->vpp" to arg2 in an entry function to zfs_lookup(), I''d like to retrieve the value of one of the fields of *(this->vpp) in the return function. Something like the below (but the syntax below is not right): printf("zfs_lookup:

...quot;operation", "key", "shmid", "size", "flags", "CPU", "Wall Time"); } fbt::shmget:entry { self->key = arg0; self->size = arg1; self->flags = arg2; self->shmgettimestamp = timestamp; self->shmgetvtimestamp = vtimestamp; } fbt::shmget:return / self->shmgettimestamp / { /* operation key shmid size flags cpu wall */ printf(&...

...program function in which the probe is located." and then ... "A probe that has a module and function as part of its name is known as an anchored probe, and one that does not is known as unanchored." Here''s my question: By the above definition, "pid" and "fbt" or clearly anchored providers since their probes specify specific locations in a program. However, other providers, like "vminfo" or "proc", while they obviously fire at a specific location, are not really defined by that location, but rather by when a certain kind of...

$B!zCK@-$O40A4L5NAEPO?$r$7$FBT$D$@$1$G$9!#(B $B>/$74i$bA*$s$@J}$,$$$$$+$b!)!)$=$l$O$*G$$;$7$^$9!#(B http://www.00-love5.com/serebu/s.html $B!V(BYAHOO!$B!W!V(BGoogle$B!W$N8!:w7k2L$O$=$N%5%$%H$N?M5$!"(B $B?.MjEY!J%f!<%6!<$K$h$kEjI<!K$G=g0L$,7hDj$7$^$9!#(B $BEv%5%$%H$O8!:w%+%F%4%j(B $B!TAG?M%[%9%H!U$K$F%H%C%W%Z!&lt...

I am getting the following error: dtrace: failed to compile script /usr/local/bin/sun-dtrace-script: line 15: probe description fbt::new_cpu_mstate:entry does not match any probes The system is amd64, and running a 127112-11. Any ideas?

Hi I have a Dtrace script ( attached ) which examines memory usage, using fbt:genunix:anon_resvmem:entry & return On my T2000 it totals the 65k pages being reserved by my application, printing out the total in bytes. Seems to work well, tested with a small app that malloced < 65 K, malloced 200M and mmapeed a 16M file and it appeared to get things correct. Could I...

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 tcpout_size["TOTAL_TCP_OUT"] va...

FYI, I posted a blog a few days ago about a DTrace provider for NFS that is currently in development: http://blogs.sun.com/roller/page/samf?entry=a_dtrace_provider_for_nfs Let''s discuss any questions, comments, etc. here. I also advertised this on nfs-discuss at opensolaris.org. Naturally, I would expect the discussion here to be more on the specifics of DTrace, and the