Displaying 20 results from an estimated 400 matches similar to: "return from memset on mac osx"
2009 Sep 09
4
usdt probes vs pid$target
I added a couple of static probes to Firefox to measure actual work
done. I could have used a pid$target probe with a function name but
work is done within an if statement, which is where I placed the
static probes.
I''m wondering about my use, though. Is the following significantly
more efficient than pid$target::FunName:entry and return?
I heard somewhere that $target does not
2009 Sep 09
10
dtrace overhead and proper measuring technique
I''m trying to time a function within Firefoxwith a pid$target probe
[2]. e.g
dtrace -Zqw -x dynvarsize=64m -x evaltime=preinit -p 13954 -s menu-
construct.d -s sigcont.d
elapsed: 12.7942481ms
cpu : 7.7911194ms
count : 40 times
I''m also measuring Firefox startup time by running it arguments like
this:
... file:///Users/joelr/work/mozilla/startup/startup.html#`python
2008 Jul 24
5
printa stddev error
Hi,
Searched for similar errors and nothing came up. Anybody know what this is?
When using aggregate stddev, and then trying to print it at END, using printa, I get this error:
dtrace: processing aborted: Invalid return value from callback
avg works fine. Tried on two recent builds of solaris (build 89 and build 94), on two difference sparc systems.
Here''s a sample script:
2007 Feb 15
2
profile provider: is it me doing stupid things?
Just showing someone how great DTrace is and then we spot something I do not understand.
Of course it can be a major misunderstanding of myself. Would appreciate another (expert) look upon this.
The goal we try to achieve is trying to get insight if there is a bursty nature in the time slot when system calls are done. Following DTrace snippet is tried:
dtrace -q -p 3173 -n
2007 Nov 14
10
[GE users] Apple Leopard has dtrace -- anyone used the SGE probes/scripts yet?
Hi,
Chris (cc) and I try to get the SGE master monitor work with Apple Leopard
dtrace. Unfortunately we are stuck with the error msg below.
Anyone having an idea what could be the cause? What I can rule out as
cause is function inlining for the reasons explained below.
Background information on SGE master monitor implementation is under
http://wiki.gridengine.info/wiki/index.php/Dtrace
2009 Apr 22
6
PID provider can not create memcpy:return probe for 64bit process
I have found that pid provider can not create memcpy:return probe for
64bit process on snv_110. For example, the pid is 10603, I will have
following output for dtrace command:
#dtrace -n pid10603:libc.so.1:memcpy:return
dtrace: invalid probe specifier pid10603:libc.so.1:memcpy:return:
probe description pid10603:libc.so.1:memcpy:return does not match any probes
This just
2010 Aug 10
2
USDT probes
Hi,
I''m posting a question hoping someone will know the answer off hand thereby reducing my search time. :-)
With USDT probes, the tracepoint is only installed by libdtrace itself, never by the drti ioctl. So whenever I run a program with an USDT probe, no tracepoint is installed. Only after I run the dtrace command the tracepoint is actually installed on the victim process.
My question
2012 Jul 03
1
buildworld fails with clang
Hello,
9-STABLE fails to build with clang and *without* "NO_WERROR=" and
"WERROR=" in /etc/make.conf. It used to work not long before :
FreeBSD zozo.afpicl.lan 9.0-STABLE FreeBSD 9.0-STABLE #0 r237222M: Mon
Jun 18 10:18:54 CEST 2012
root@zozo.afpicl.lan:/usr/obj/usr/src/sys/CORE amd64
# svnversion
238067M
# make NOCLEAN=yes NO_CLEAN=yes buildworld
[...]
===> cddl/lib
2008 Mar 03
4
Modifying macro names generated by dtrace -h
I''d like to prepend TRACE_ to the macro names generated by dtrace -h.
For example, change
POSTGRESQL_LWLOCK_ACQUIRE(arg0, arg1) to
TRACE_POSTGRESQL_LWLOCK_ACQUIRE(arg0, arg1) and still keep postgresql as
the provider name. The reason for doing this is to make it clear that
the macros are used for (D)tracing. In this particular case, without
TRACE_, it appears like the macro is used
2008 Dec 01
7
DIF content is invalid?
What''s going on?
# dtrace -s iotime_all.d 100
dtrace: failed to enable ''iotime_all.d'': DIF program content is invalid
The errant script....
#pragma D option quiet
BEGIN
{
stime = timestamp;
io_count = 0;
}
io:::start
/args[2]->fi_pathname != "<none>"/
{
start[pid, args[2]->fi_pathname, args[0]->b_edev, args[0]->b_blkno,
2006 Dec 07
1
When does ufunc/func work?
I''m trying to profile the time spent in libc functions in a large build job (building Perl), and I have trouble getting 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;
2006 Sep 21
2
Probe description does not match any probes
[Perhaps someone could rename this list to dtrace-matt-problems-discuss?]
If I run this script against my binary (which contains a USDT probe called ''concurrentq-latency''):
:::
/ probename == "concurrentq-latency" /
{
printf("[%s]:[%s]:[%s]\n", probeprov, probefunc, probename);
}
I get this output:
dtrace: script ''testq.d'' matched 46056
2008 Feb 26
11
Is there way to trace memory in the dtrace ?
N_conreq:entry {
self->x=1;
calledaddr=(struct xaddrf *)arg3;
callingaddr=(struct xaddrf *)arg4;
trace(calledaddr->link_id);
tracemem(calledaddr->DTE_MAC.lsap_add, 80);
trace(callingaddr->link_id);
tracemem(callingaddr->DTE_MAC.lsap_add, 80);
}
0 -> N_conreq 255
2005 Dec 22
9
truncating aggregation output only
Hello dtrace-discuss,
Sometimes I want to run a script for some time and every n second
output N top entries. trunc() isn''t suitable here as it also removed
keys/values. I want it ''coz over time if I use sum() entries which
are normally truncated can actually get to top over a time.
Maybe printa() extension, something like: printa(@b[10]) - to output
top 10?
--
2006 Mar 03
10
CiscoWorks 2.5 Install on Solaris 10
I''m trying to install CiscoWorks 2.5 on Solaris 10 update 1, and after
the install when I try to start the daemon, it errors:
# /opt/CSCOpx/objects/dmgt/dmgtd.sol
ERROR: open file dmgtd failedERROR >>>>>>>>>>>>> open msg catalog
failed. NLSPATH incorrect or objects/share/nls/C/dmgtd.cat is missing.
# echo $NLSPATH
2006 Aug 14
1
Why does dtrace -h remove const qualifier?
If I have the following definition:
provider foo {
probe bar(const char*);
};
and creates the headerfile (snv 43) with dtrace -h I get:
extern void __dtrace_foo___bar(char *);
This is a "problem" for me (ok, I could add an explicit cast each time I fire the probe, or edit the generated headerfile by hand...), since it generates compilation errors when I call the probe in a C++
2005 Sep 22
0
io provider and files in a forceddirectio mounted filesystem
The following script is used as a first attempt to discover IO patterns in a
dbase setup:
#------------------------------------------------------------------
#pragma D option dynvarsize=128m
dtrace:::BEGIN
{
}
pid$target::kaio:entry
{
self->doit = 1;
}
pid$target::_aiodone:return
{
self->doit = 0;
}
io:::start
/self->doit || execname == "oracle"/
{
2007 Feb 13
2
zpool export consumes whole CPU and takes more than 30 minutes to complete
Hi.
T2000 1.2GHz 8-core, 32GB RAM, S10U3, zil_disable=1.
Command ''zpool export f3-2'' is hung for 30 minutes now and still is going.
Nothing else is running on the server. I can see one CPU being 100% in SYS like:
bash-3.00# mpstat 1
[...]
CPU minf mjf xcal intr ithr csw icsw migr smtx srw syscl usr sys wt idl
0 0 0 67 220 110 20 0 0 0 0
2006 Jun 03
8
dtrace causing sigtrap?
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
2009 Mar 20
1
suspicious dtrace results
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;