Displaying 20 results from an estimated 1500 matches similar to: "Question about -xlaxyload option to dtrace -G"
2008 Jan 29
12
listing USDT probes, if any
How do I query an application to see if it supports any USDT probe points?
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
2007 Sep 01
1
Hekp dtrace -l is bleeding Unstable implementation details all over my USDT probe namespace :(
Hi,
As I''ve discussed before whenever we add USDT probes to a C++ function
and call dtrace -l we get the mangled C++ name for the dtrace function,
being listed :(
Now the point of USDT probes is to abstract a higher level semantic
construct for users to make use of. Surely it is not meant to be listing
Unstable Interfaces (implementation details), such as the containing C++
2007 Oct 29
2
autoconf test for building dtrace USDT probes?
X.Org has adopted GNU autoconf as its build configuration mechanism,
so when I integrated the dtrace probes, I checked to see if they
should be built using this test, checking for the existence of a
program named "dtrace" in the path:
dnl Check for dtrace program (needed to build Xserver dtrace probes)
AC_ARG_WITH(dtrace, AS_HELP_STRING([--with-dtrace=PATH],
[Enable dtrace
2007 Jun 07
2
plockstat/dtrace core dump S10U3
Hey,
Im able to reproduce a crash from plockstat everytime Im tracing a JVM pid. I do recall a problem related with this one, but not clear if this has been fixed in U3 or is it planned for U4 ? Any BugID opened for this stack trace:
> ::stack
libc.so.1`strlen+0x50(100003faa, ffffffff7ffff5c8, ffffffff7eca1114, ffffffff7fffec79, 0, 100003fa9)
libc.so.1`snprintf+0x88(ffffffff7ffff8f0, 0,
2009 Sep 18
7
Why is plockstat provider only present for 1 process
Hi,
I would like to know why dtrace -l |grep plockstat show plockstat28099
lines.
Process with pid 28099 is a java process.
Why can I not examine other processes with the plockstat provider?
Is it a java startup option?
Regards Hans
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
2018 Aug 23
2
[lld] avoid emitting PLT entries for ifuncs
In the context of support not only IFunc but DTrace, what kind of features
do you want to add to lld, if you have a chance to implement it in the
linker instead of a post-processing tool? I wonder if we can solve both of
your problems.
On Thu, Aug 23, 2018 at 1:33 AM Mark Johnston <markj at freebsd.org> wrote:
> On Wed, Aug 22, 2018 at 10:11:00AM -0400, Ed Maste wrote:
> > On 22
2008 Oct 30
7
Is there any way to check if DTrace is running or a DTrace probe is enabled?
Hi,
I am adding DTrace probes within NFS v3 client. In my current
implementation, I use some tsd_*() functions and kmem_zalloc() function.
These functions might be heavy and affect the performance. I want to
call this function only when DTrace is running or the DTrace probes are
enable. So is there a way to check DTrace is running or DTrace probe is
enabled?
Regards,
Danhua
2008 Nov 24
1
DTrace helper interface''s deprecated ioctls
Hi,
Is there a specific reason the DTRACEHIOC_REMOVE ioctl is deprecated?
I found I needed to use it in my Perl USDT provider code[*], which
creates providers dynamically at runtime. I wonder if I''m missing a
better way of doing the same thing.
The situation I''m handling with the remove operation is killing and
recreating a perl interpreter in the same process, which
2008 Sep 16
3
USDT probes in both static library and application
Hi All,
I''ve got a problem when I have USDT probes in a static library and in
the application code outside of the library.
I build the static library containing some USDT probes, glomming
everything together (ld -r) before creating the .a file to preserve the
probe symbols. This all works fine.
I build an application which also has some USDT probes.
When I build the application which
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
2006 Jul 06
4
plockstat - chopped stack output
Hi - I''m trying to use plockstat to help identify any mutex contention issues we may have in our c++ app.
>From the docs it would appear to be a very useful tool - unfortunately in practice this doesn''t bear out purely because the stack traces produced are limited to being 39/40 characters wide. In general this means that I''m not seeing ~75% of each stack symbol and
2008 Nov 05
2
plockstat: processing aborted: Abort due to systemic unresponsiveness
Hello,
I need help here about plockstat on X86 platform (Sun X4600 AMD)
# plockstat -A -p 20034
plockstat: processing aborted: Abort due to systemic unresponsiveness
# plockstat -e 5 -s 10 -A -x bufsize=100k -x aggsize=20m -p 20034
plockstat: processing aborted: Abort due to systemic unresponsiveness
# ps -ef | grep 20034
algodev 20034 1 2 07:00:54 ? 86:17
2007 Mar 09
4
USDT probe issues in C++
Hi people,
When working with some usdt C++ probes we have come across a few issues.
Controlling USDT Function name:
Putting in usdt probes into C++ code gives you the mangled enclosing
function name for the probes Function name. Working around this can be a
pain. You need to wrap your usdt probes in extern C functions and call
these. Could we have an option to control the Function name for
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
2006 Aug 07
2
SDT/USDT policies?
Hello,
If I release a new kernel module, do I need to release a SDT provider with it? Just like what "mdb" does - a mdb module together with the associated kernel module. Is it a "MUST" or a "OPTION"?
Also what''s the requirement of USDT and user application? Is it encouraged or not to have many probes inside the code? Can I define my own
2008 Apr 18
2
plockstat: failed to add to aggregate: Abort due to drop
when check java process lock statistics, plockstat failed, please see below:
# prstat -mLp 21162
PID USERNAME USR SYS TRP TFL DFL LCK SLP LAT VCX ICX SCL SIG PROCESS/LWPID
21162 7677 0.9 0.1 0.0 0.0 0.0 99 0.0 0.3 83 89 215 0 java/81
21162 7677 0.3 0.1 0.0 0.0 0.0 0.0 99 0.2 106 33 305 0 java/35
21162 7677 0.1 0.0 0.0 0.0 0.0 100 0.0 0.1 79 6 85 0 java/59
2006 Oct 31
0
6256581 System got a hang or a panic with dtrace+kmdb
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
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 Sep 30
12
dtrace missing ''unlinkat''? showing process stack?
everyone,
Just out of curiosity, I did a
dtrace -n ''syscall:::entry { @num[execname, probefunc] = count(); }''
and looked at the entries produced by ''rm''.
I see everything that rm did, *except* the unlinkat - which is unfortunate because I want to trace which processes have deleted which files.
So - does dtrace contain unlinkat as a probe for a system call?