Displaying 5 results from an estimated 5 matches for "stackdepth".
Did you mean:
stack_depth
2011 Apr 06
2
Limiting dtrace depth
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
2006 Feb 15
4
Script for Stackdepth by Thread/LWP?
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 opensolaris.org
2006 Oct 31
0
4970475 There should be a stackdepth equivalent for userland
Author: ahl
Repository: /hg/zfs-crypto/gate
Revision: a2677fc0a5fb6895ed56fc4698646ece44978a48
Log message:
4970475 There should be a stackdepth equivalent for userland
5084954 value of dip can be incorrect in autovec
6181505 dtrace sysinfo:::modload probe does not fire when using ''modload''
6265417 schedctl-yield isn''t listed in sdt_subr.c
6272558 gcc and dtrace don''t get along
6276101 dtrace -G behaves s...
2005 Nov 15
6
Oracle 9 process on Sol 10 container, doing a pollsys, using high CPU
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%
2006 Feb 17
3
CPU time stats
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);}