similar to: Dtrace not working for processes running after a couple of hours

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

Hello experts, I heard that there is something called anonymous dtrace that would still be running when I do a reboot. Basically, I have the following problem: The /boot/solaris/bootenv.rc file in my alternate boot environment is getting modified when I reboot the machine after doing luactivate <ABE>. It happens only on init 6, doesn''t happen when I do a simple reboot. The set

OK, First, thanks for all of the help recently. I appreciate it. But...I have just implemented the cvs code as to be able to use the 'use client driver' option because win nt/2k machines have been seeing an 'Access denied, unable to connect' error for the print queues and this will apparently fix this. I will describe my setup and what I have done thus far: RH 7.1 Samba 2_2 cvs

Can i use dtrace to anlayze my core files ? -- This message posted from opensolaris.org

Hi, I am adding DTrace probes within NFS v3 client. In my current implementation, I use some tsd_*() functions and kmem_zalloc() function. These functions might be heavy and affect the performance. I want to call this function only when DTrace is running or the DTrace probes are enable. So is there a way to check DTrace is running or DTrace probe is enabled? Regards, Danhua

I have a number of systems running solaris10 and i see the package and binary for dtrace installed however whenever we try to run anything we get this error dtrace: failed to initialize dtrace: DTrace device not available on system the only system in which i dont have this error is the development server that has the full solaris 10 install while others are minimized, do i need additional

Hi all, How to dtrace a who is writing a veritas volume? Thanks. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.opensolaris.org/pipermail/zfs-discuss/attachments/20070412/dfd8c254/attachment.html>

Greetings, is there a way to specify probes and other dtrace operations via command line parameters, like " BEGIN { usr_exec=$$1; usr_syscall=$$2; } syscall::usr_syscall:entry /execname == usr_exec && guard++ == 0/ { ... " [this does not work] This would make it possible to create "generic" dtrace scripts. Otherwise, some shellscript with sed-magic would

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 am trying to trace some functions that are executed at detach time, and it seems that just having dtrace around to instrument the module is causing a short circuit, whereas modunload will return (device busy). I understand that this makes sense, but how can I get around this if I want to trace stuff at detach time? Thanks, --S

Hi, I have mentioned before that we have added some sdt dtrace probes in SAX, our APL interpreter. Encouraged by Angelo and Jignesh, I have created a small document (5 pages) describing our experience with it, together with some problems we have encountered and some scripts we use for pretty-printing dtrace outputs. The said document can be found at

Hi, As I''ve discussed before whenever we add USDT probes to a C++ function and call dtrace -l we get the mangled C++ name for the dtrace function, being listed :( Now the point of USDT probes is to abstract a higher level semantic construct for users to make use of. Surely it is not meant to be listing Unstable Interfaces (implementation details), such as the containing C++

Hi all, We just got a shiny new T5440, and one of the first things I noticed (besides the insane number of hardware contexts), is that dtrace takes 30 seconds to a minute to fire up scripts with 5-6 probes, where our T5220 usually takes under a second. Shutdown is similar, though slightly faster. This is mostly annoying because it takes so long to attach that it''s hard to tell when

Dtrace does work on some workstation, such as as follows, ----------------------------------------------------------- bash-3.00# dtrace -s ./mem.d `pgrep test` dtrace: script ''./mem.d'' matched 5 probes ^C bash-3.00# uname -a SunOS ftp 5.10 Generic_118833-17 sun4u sparc SUNW,Sun-Blade-100 bash-3.00# dtrace -V dtrace: Sun D 1.1

I use a lot of tabs and Firefox runs very slowly. I would like to figure out which tabs are eating up resources (cpu, memory, etc). Will the Mozilla dtrace framework be any help with this? -- This message posted from opensolaris.org

I''m pleased to pass along news that the Mac OS X DTrace port has been updated in 10.5.3 to fix the issue that caused timer based probes not to fire in the presence of certain untraceable applications. http://blogs.sun.com/ahl/entry/apple_updates_dtrace A big thank you to the folks at Apple for addressing the problem. Adam -- Adam Leventhal, Fishworks

Howdy, I installed Nevada build 49 in a parallels VM on my intel mac mini, and when I run the following DTrace script: $ cat follow.d #pragma option D flowindent; pid$target:::entry, pid$target:::return {} $ cat format.cmds disk 0 exit $ dtrace -s follow.d -o follow.out -c "/usr/sbin/format -f format.cmds" dtrace: script ''follow.d'' matched 13641 probes The system

Hi All, One of the customer is seeing the following error messages. He is using a S10U1 system with all latest patches. Dtrace script is attached. I am not seeing these error messages on S10U2 system. What could be the problem? Thanks, Gangadhar. ------------------------------------------------------------------------ rroberto at njengsunu60-2:~$ dtrace -AFs /lib/svc/share/kcfd.d dtrace:

Hi all, There''s a dead thread about this back at http://forums.sun.com/thread.jspa?threadID=5075157, but it would be really nice to have support for if/else control flow in actions. Reasons: 1. The ternary operator ?: is already there (though it doesn''t let you do anything with side effects) 2. The user can already write arbitrary and expensive non-cacheable predicates if

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