search for: progenyof

...dress (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 error messages. Below is some D-program codes: . . syscall::open:entry /!progenyof($pid) && copyinstr(arg0) == "/opt/SUNWvts/bin/sparcv9/../../lib/sparcv9/libvtstest.so.1"/ { stop(); system("qtracepid.d %d %s &", pid, basename(copyinstr(arg0))); } . . syscall::open:entry /!loaded[copyinstr(arg0)] && !progenyof($pid) && copy...

Hi, I am tracking down a problem and would like to know how I can follow a forked process with my dtrace script, or how I can trace a dynamic library. Here is the problem. I am tracing dtlogin, and specifically I am trying to determine what error libpkcs11`<routine> is returning. It turns out dtlogin forks a lot of processes, and I believe the second forked process is the one that winds

Just to let people know what my big picture is, I''m trying to write a script that will let me run a program, and name a progeny of that program that I want to debug. My script should find the first occurrence of that progeny, and run it until it finishes initializing the runtime linker, but stop it before it runs any shared library startup routines. (Failing that, I''d be okay

...g ufunc and func working. (func() is not strictly needed; I was just hoping to use it in order to profile idle time.) Here''s the story. I''ve written a dtrace script to start a separate dtrace process for each invoked command: int fileid; proc:::exec-success /pid == $target || progenyof($target)/ { self->traceme = 1; @proc[execname] = count(); } /* This should fire AFTER libc has been dloaded. */ syscall::setcontext:entry /self->traceme/ { self->traceme = 0; stop(); system("dtrace -q -s /export/home/dds/src/dtrace/libc.d -o /e...

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.

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%

Suppose I have a USDT probe in Firefox and that I''m trying to catch the startup with a probe like this: proc:::exec-success /execname == "firefox-bin"/ { start = timestamp; } and stop tracing when Firefox hits this USDT probe: mozilla:::main-entry { exit(0); } How do I put the running firefox-bin into "trace mode" so that my USDT probe fires? Thanks, Joel