similar to: System hangs when invoking DTrace script

So I realize this is somewhat stupid, and I''ve actually gotten myself out of kmdb to kill my dtrace script but this has happened in the past and I''m wondering if there''s any better way around it than hitting :c a bunch of times. Say you set a breakpoint() to fire in a common function. This will drop you into kmdb where you can do some debugging, you take a look around

Hi, is it somehow possible to use Dtrace for error injection in a kernel module? Something like changing: - function return value - value of a register If not, can it be implemented? I can do that via kmdb, but I need Dtrace for the time synchronization - chill() action. I can not combine Dtrace & kmdb: dtrace: failed to initialize dtrace: DTrace cannot be used when kernel debugger

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

Howdy, I am attempting to isolate the location of a memory leak in a 4GL program, and have hit a bit of a snag. When I LD_PRELOAD libumem and run the application server, "::findleaks -fdv" reports numerous leaks: CACHE LEAKED BUFCTL CALLER 0000000100b49068 15 0000000100ef2d50 fdcon+0x6c4 0000000100b50028 1 0000000100b72ac0 fdcon+0x6c4 0000000100b49068

I am trying to use dtrace to trace all sscanf calls. I am able to use pid provider for this. But my application forks off children at times to handle requests. Is there a way I can stop the child process immediately after it is started so that I can attach a pid provider to that and trace the scanf calls in it? I have tried using the "create" probe but that did not help.

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

Howdy, I am trying to migrate several scripts to use application defined types, and am running into a few issues. When I attempt to run a script with a application defined type, it looks like the DTrace preprocessor is getting angry with me: $ cat view.d #include "httpd.h" :::acceptconnection { this->addr = (conn_rec *)copyin(arg0,sizeof(conn_rec *)); } $ dtrace -C

The open solaris dtrace page (http://www.opensolaris.org/os/community/dtrace/) has a bad link to the DTrace Guide(http://docs.sun.com/db/doc/817-6223). This message posted from opensolaris.org

Hello, all experts. When I use pid provider, my Dscript with -F option output the codepath with flowindent as you know, e.g. -> main -> f1 -> f2 however I realized that the exec file I used at that time was stripped. Does anyone know the reason why I could see the function names? Thanks in advance. -- This message posted from opensolaris.org

Hi, all, I''m a newbie on dtrace and the problem I am having is: For processes which have been running for more than a couple of hours, dtrace doesn''t seem to be able to trace(I waited for at least one hour and didn''t see anything happening). However, it works every time for a relatively new process. Any insight or help will be appreciated. This is my machine:

We''re running a Solaris 10 container, with an Oracle 9.2.0.4 database - every 5-10 min, an Oracle process shoots up (using 20% + CPU) and then goes down in CPU %, doing a [i]pollsys [/i](see it via dtruss). I tried using some of the trace scripts in the Dtracetoolkit to see what the process is doing, but without any luck - also tried with the following, but dtrace process goes up to 30%

Author: bmc Repository: /hg/zfs-crypto/gate Revision: 213bfe03af413cdf71c523fb076aaa65a6306a7e Log message: 6256581 System got a hang or a panic with dtrace+kmdb 6264573 unanchored dtrace_getpcstack is rather imprecise toward function end 6289517 dtrace doesn''t like fd_intr anymore 6291378 dtrace helpers can interfere with the use of kmdb 6295554 dtrace doesn''t report

Oh I see. Thank you. I will study that. Journeyer 2013/1/13 Sean Silva <silvas at purdue.edu>: > You can easily collect this information with DTrace on a Mac (or > Solaris or FreeBSD) without any special LLVM instrumentation. > > -- Sean Silva -- ---------------------------------------- Journeyer J. Joh o o s a p r o g r a m m e r a t g m a i l d o t c o m

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

A small script to see what SCSI commands are being issued by a system: http://blogs.sun.com/roller/page/chrisg?entry=scsi_d_script Still work in progress as I needs to handle larger CDBs but it is a start, since I don''t have a disk that big it is not a problem for me yet. Also getting the return scsi packet is a hack but so far I can see no alternative short of knowing about all the

------------------forwarded------------------------------------ This is to help my customer to migrate their IBM websphere 6.0.2 to run on solaris 10 platform. Customer is eager to use the dtrace agent of JDK (https://solaris10-dtrace-vm-agents.dev.java.net/ ) to benefit their IBM websphere server, I am not sure whether we can use this agent in IBM websphere bundled JDK whose version is JDK

hi, i want to find out the total number of incoming connections for a machine at any time using dtrace.anyone please suggest me the solution. This message posted from opensolaris.org

On Sat, Jan 12, 2013 at 10:00 PM, Journeyer J. Joh <oosaprogrammer at gmail.com> wrote: > Oh I see. Thank you. I will study that. You will want to use the pid provider. The most basic thing you can probably do is to turn on flowindent and just trace `pid$target:::entry' and `pid$target:::return`, which will trace all the function calls and returns. This blog post

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;