similar to: strange problem on SXDE3

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

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

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

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

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;

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

Hi, I''ve a b81 server running for a while. I''ve done all sorts of Python related stuff on it (nothing amazing, mostly compiled python2.5 and iPython in /usr/local), and now am trying to use it with xVM to install Windows on a virtual machine in it. I''m having trouble creating the new machine, and I get a blank error response like so when I try to do it:

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,

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

Hy! I receive an nxge driver messages on console: Aug 18 11:08:42 [hostname] nxge: NOTICE: nxge_ipp_eccue_valid_check: rd_ptr = XXX wr_ptr = YYY I find the bug description/correction at sun web page, and i know i can ignore it. I thinking about how can i delete from console only these messages (here is my first version, what is not (so) elegant): #!/usr/sbin/dtrace -qs #pragma D option

Hi, Has something related to speculative tracing changed between s10 FCS and the more recent nevada builds ? I was trying the specopen.d script from the Dtrace guide on a nevada machine and it failed with : dtrace: failed to enable ''./spec.d'': DIF program content is invalid To try and narrow things down a bit I wrote the following short script. This works fine on s10, but

I got a system that is hung, unable to do most unix commands like ps/who etc... I did: dtrace -c /usr/bin/ps -n ''pid$target::open*:entry {printf("%s %s",execname,copyinstr(arg0)); }'' and it hangs here: 7 65277 open:entry ps /proc/19729/psinfo 7 65277 open:entry ps /proc/11687/psinfo ^C So, I tried to kill -9 11687,

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

(PS: another idea that comes along the same lines as a dumper function and IMO would be helpful is an ''introspect'' function. Given an argument: introspect(probefunc) it returns back the expected arguments for the probe func, their datastructures, as well as the syntax on how to dereference them. If an intelligent copyinstr comes out, this would be easy to write, and would

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);

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

G''Day Folks, I''ve found another use of dtrace, this makes your console keyboard sound like a typewriter. http://www.brendangregg.com/DTrace/typewriter-0.70.tar.gz I''ve only tested it on an UltraSPARC 5 and a Pentium laptop so far, more to follow. Ok, sorry, not actually a practical use of DTrace. :) Enjoy! Brendan [Sydney, Australia]

hi fnds, i want to print the filenames on which the stat system call is acting when a stat system call is invoked. can anyone can help me this regard. Thanks jeevan

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

Hi, I have a situation where a DTrace script is printing out extra characters, despite the copyin() call giving a specific length. Can anyone think of why this might be? It''s fine the first time all of the probes fire, but on a second run of my generating operations, I get junk in there. For example: set setop length 5, FOUND KEY, STORED set setop length 5, FOUND KEY, STORED get