similar to: 4970475 There should be a stackdepth equivalent for userland

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

I''m interested in monitoring the amount of stack used by a multi-threaded program. I assume ''stackdepth'' built-in would be useful...but not sure. Been through demo''s, ToolKit, and internals..but it''s just not clicking for me yet. Not sure how to measure start/end of stack size dynamically...Anyone know how to break this down? This message posted from

Author: bmc Repository: /hg/zfs-crypto/gate Revision: 7f6ac6a8f8587aa1bf748eb29f8c942583047d10 Log message: PSARC 2006/196 DTrace Filesystem Info Provider 6405662 add DTrace fsinfo provider Files: update: usr/src/lib/libdtrace/common/io.d.in update: usr/src/uts/common/dtrace/sdt_subr.c update: usr/src/uts/common/fs/vnode.c

If I use a simple dtrace script such as this: fbt::somefunc:entry{self->trace=1;} fbt::somefunc:return{self->trace=0;} fbt:::entry{} fbt:::return{printf("%lx", arg1);} then it will descend to whatever depth is necessary If I want to limit it to say 3 functions deep, how can I do that? The quick answer I want to use is to do "self->depth++" on each entry and then

> There are times when arg0 can be NULL [for the interrupt-start or > interrupt-complete probe] if there''s no associated device. > There''s already a bug open to address the error in the documentation. > 6284911 args to interrupt-start and interrupt-complete need more info Hmm, I noticed that, too. There''s currently a thread on yahoo''s solarisx86

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: anish Repository: /hg/zfs-crypto/gate Revision: 445b09139fca7f498d4a47a7a31fc69e742dd484 Log message: 6414036 ::interrupts share_cnt can be misleading 6415576 add new options to ::interrupts for displaying intrstat like output etc. Files: update: usr/src/cmd/mdb/i86pc/modules/pcplusmp/apic.c update: usr/src/cmd/mdb/i86pc/modules/uppc/uppc.c

hi, I am trying to find out the avg cpu time spent in each of my user methods (exclusive of other methods invoked by a method). Hence the following snippet failed miserably: ----------------------- pid$target:a.out::entry { time[probefunc] = timestamp;} pid$target:a.out::return { @spent[probefunc] = avg(timestamp - time[probefunc]);} END { printa(@spent);}

Author: tomee Repository: /hg/zfs-crypto/gate Revision: 367993089b181886f94c88ffa5759d0626e95ad7 Log message: PSARC 2006/054 DTrace JNI Binding 6384263 PSARC 2006/054 DTrace JNI Binding Files: create: usr/src/lib/libdtrace_jni/Makefile create: usr/src/lib/libdtrace_jni/Makefile.com create: usr/src/lib/libdtrace_jni/amd64/Makefile create: usr/src/lib/libdtrace_jni/common/dtj_attr.c create: