Displaying 3 results from an estimated 3 matches for "probeprov".
Did you mean:
phoneprov
2006 Sep 21
2
Probe description does not match any probes
[Perhaps someone could rename this list to dtrace-matt-problems-discuss?]
If I run this script against my binary (which contains a USDT probe called ''concurrentq-latency''):
:::
/ probename == "concurrentq-latency" /
{
printf("[%s]:[%s]:[%s]\n", probeprov, probefunc, probename);
}
I get this output:
dtrace: script ''testq.d'' matched 46056 probes
dtrace: pid 26257 has exited
CPU ID FUNCTION:NAME
2 46076 dequeue_thread:concurrentq-latency [tests26257]:[dequeue_thread]:[concurrentq-latency]
However, if I tr...
2007 Jan 10
13
[DTrace] how to get socket read size
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
2007 Dec 29
1
why was some stack information lost.
...T);
while(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]...