search for: probemod

...executable and then dynamically create a dscript to trace execution of those modules alone (by excluding the 3rd party and system libraries). I tried the below script without success. The conditional given in the predicate is not taking effect. Why is this so ? $ dtrace -ln ''pid$target::: /probemod!="libc.so.1"/ { printf("%s ----- %s",probefunc, probename); } '' -p `pgrep a.out` Similar is the case for the below script, I expect only the entry points to be printed but all the probes in a.out are being printed. $ dtrace -ln ''pid$target:a.out:: /probename==...

Referring to the DTrace manual: "Module If this probe corresponds to a specific program location, the name of the module in which the probe is located. This name is either the name of a kernel module or the name of a user library. Function If this probe corresponds to a specific program location, the name of the program function in which the probe is located." and then ...

Hi i''m trying to write my first dtrace script apparently i bit off a bit more than i can chew, i want to track io over sockets, i found your socketsize.d that gave me how to track writes, but i''m at a loss how to track reads, frankly i don''t see how your write tracker works because it uses a probe in a function that only takes two arguments but you grab size of write

...1) { sleep(1); write(fd,value,strlen(value)); } } //////////////////////////////////////// and the dtrace script (write.d) is: syscall::write:entry, fbt::write:entry, pid$1::write:entry, pid$1::write:return, pid$1::_write:entry /pid==$1/ { printf("%s:%s:%s:%s\n",probeprov,probemod,probefunc,probename); stack(100); ustack(100); } /////////////////////////////// when runs the script, the result is : pid17632:libc.so.1:write:entry libc.so.1`write a.out`main+0x43 a.out`_start+0x7a pid17632:libc.so.1:_write:entry [b] libc.so....

...unix`thread_start+0x4 2608 unix`cpu_halt+0xc8 unix`idle+0x128 unix`thread_start+0x4 287026 bash-3.00# bash-3.00# dtrace -n fbt:::entry''{self->vt=vtimestamp;}'' -n fbt:::return''/self->vt/{@[probemod,probefunc]=sum(vtimestamp-self->vt);}'' -n tick-10s''{trunc(@,20);printa(@);exit(0);}'' dtrace: description ''fbt:::entry'' matched 24134 probes dtrace: description ''fbt:::return'' matched 24091 probes dtrace: description ''tick-10...

Hola, I am trying to isolate the memory leak I suspect in a mailman installation ? I found: http://blogs.sun.com/sanjeevb/date/200506 It gives an error: god at irt-smtp-02:~ 9:21am 65 # ./memleak.d 10312 dtrace: failed to compile script ./memleak.d: line 3: probe description pid10312:libc.so.1:malloc:entry does not match any probes I am on SunOS 5.10 Generic_127112-07 i86pc i386 i86pc Are