Displaying 20 results from an estimated 10000 matches similar to: "''introspect'' method"
2008 Sep 30
12
dtrace missing ''unlinkat''? showing process stack?
everyone,
Just out of curiosity, I did a
dtrace -n ''syscall:::entry { @num[execname, probefunc] = count(); }''
and looked at the entries produced by ''rm''.
I see everything that rm did, *except* the unlinkat - which is unfortunate because I want to trace which processes have deleted which files.
So - does dtrace contain unlinkat as a probe for a system call?
2008 Apr 20
1
dtrace script to monitor file access
A user has asked us to find out who is changing one of their files and how it is being changed. I came up
with the script below:
#!/usr/sbin/dtrace -s
#pragma D option quiet
BEGIN
{
printf("\n Timestamp gid uid pid ppid execname function current directory file name\n\n");
}
syscall::open:entry,
2008 Jan 04
0
How do I print wide char string arguments!
Hopefully this is a straight forward issue and I''m missing
something obvious.
I''m trying to print a wchar_t [] argument from a simple example
program like
#include <stdio.h>
#include <wchar.h>
#include <unistd.h>
void
prout(wchar_t *wstr)
{
}
int
main()
{
wchar_t name[]=L"Angelo Rajadurai";
int i;
for(i=0; i<1000 ; i++)
{
prout(name);
2008 May 20
6
Dtrace queries - predicates & func arg tracing
[1] Predicates in one-liners
I would like to list the probe modules in my 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:::
2011 Jan 05
0
dtrace-discuss Digest, Vol 69, Issue 2
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
2006 Sep 06
3
Dtrace Snooping
Dear dtrace Experts,
I have seen some dtrace utilities like opensnoop and execsnoop etc.
My interest is to write a simple script that can snoop the files which
uses the 3 syscalls like open,create,unlink.
I have gone through dtrace oneliners that can do the same :
dtrace -n ''syscall::open*:entry { printf("%s %s",execname,copyinstr(arg0));}''
dtrace -n
2006 Mar 16
0
Re: Can dtrace agent of JDK be used in IBM Websphere?
Hi, Yufei:
Thanks for your kind action.
Let me centralize all the harm-hearted guys and involved alias in one email.
Below is the answer of your question (Can you reply with more details on
what failed? Does websphere use an IBM or Sun developed SDK? )
1. Seems IBM bundled JDK can not detect agent options, like below:
If use Sun JDK 1.5, no problem:
/usr/jdk/jdk1.5.0_06/bin/java
2005 Sep 27
2
Invalid address error message
Hi,
I ran a d-program with syscall::open:entry probe but got the following
error messages sometimes:
dtrace: error on enabled probe ID 1 (ID 14: syscall::open:entry): invalid
address (0xff34e000) in predicate at DIF offset 76
dtrace: error on enabled probe ID 6 (ID 14: syscall::open:entry): invalid
address (0xff34e000) in predicate at DIF offset 28
I don''t know how to interpret these
2011 Jan 05
0
Understand the dtrace quantize output
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;
2006 Sep 12
3
dtrace reports different counts depending on what is being traced
We are using following dtrace script to analyze an application. However
we see different number of lwp_yield and yield calls reported depending
on whether we trace mutex_lock or mutex_unlock or not. The number
reported when we are not tracing mutex_lock or mutex_unlock is higher.
What could be going on here and which one is the correct number. This is
on S10 U2.
Thanks,
Rao.
2009 Mar 20
1
suspicious dtrace results
i am doing reads and writes to /dev/rdsk/c0t2d0s4
using dtrace to see how much time it took for ssdread and ssdwrite. It shows very small number 4 or 5.
#pragma D option flowindent
syscall::pread:entry
{
self->trace = 1;
self->size = arg2;
}
syscall::pwrite:entry
{
self->trace = 1;
self->size = arg2;
}
fbt:ssd:ssdread:entry
/self->trace/
{
self->start = timestamp;
2007 Oct 01
1
strange problem on SXDE3
Strange problem on a desktop, 64 bit, SXDE3.
] ./jpg1.d
dtrace: failed to compile script ./jpg1.d: "/usr/lib/dtrace/iscsi.d",
line 94: syntax error near "uiscsiproto_t"
Doesn''t matter what script. Even classic oneliners such as:
] dtrace -n ''syscall::open*:entry { printf("%s %
s",execname,copyinstr(arg0)); }''
bomb in this way...
dtrace:
2008 Jul 07
2
copyin having secondary effects.
Dtracing gethostbyname I''m trying to read the h_alias array and all the entries it points to however every time I copyin an entry pointed to by the first entry in teh h_alias array the other entries in the array get corrupted.
So I have ended up with this script:
#!/usr/bin/dtrace -CZs
#include <netdb.h>
pid$target::gethostbyname_r:return
{
self->r = (struct hostent
2006 May 24
2
Reading external files with dtrace
I''d like to be able to dynamically read external configuration files within a dtrace script. I know dtrace allows inclusion of C header files but only at the preprocessing stage.
What we need to do is dynamically enable/disable probes based on current application settings. I''d rather not have a bunch of independant scripts running and being started and killed whenever the
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
2007 Jul 11
5
Error trying to count return points in functions.
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
2006 Mar 01
3
vtimestamp skew, after restorectx()
Hello,
I''m using the below dtrace script to capture the flow and times of
kernel functions, from an ioctl() call. After an entry into
restorectx(), the trace of startimestamp - vtimestamp makes a dramatic
jump downwards. Here''s the snippet showing the jump...
6 -> di_checkmem 8 220176600
6 <- di_checkmem
2006 Mar 24
3
Triggering on close of a written file.
I have just started my first ''serious'' dtrace script and can use some
advice.
I want to have a probe triggered when close() occurs after a
succesfull write of /etc/hosts ( I want to regenerate the nameserver
zone files
from /etc/hosts after it has changed)
At the moment I have the following code:
syscall::open*:entry,
syscall::creat*:entry
{
self->file=arg0;
2007 Aug 09
8
Dtrace - Segmentation Fault
After building and bfu''in the lastest ON build, any time I run a dtrace script I get a Seg Fault. Is there a dtrace for dtrace :)
Doug
root at prae> dtrace -n ''syscall::open*:entry { printf("%s %s",execname,copyinstr(arg0)); }''
Segmentation Fault (core dumped)
root at prae> pstack core
core ''core'' of 101364: dtrace -n
2006 Aug 08
9
Handling userland char ** pointers
I''ve been trying to get access to a userland string that''s behind a
second level pointer using DTrace, but I can''t seem to get it to work.
I started with the example on the Team DTrace Tips and Tricks slides:
trace(copyinstr(*(uintptr_t *)copyin(arg0, curpsinfo->pr_dmodel ==
PR_MODEL_ILP32 ? 4 : 8)));
And when I couldn''t get it to work, I started