Displaying 20 results from an estimated 6000 matches similar to: "opensolaris dtrace page has bad link to dtrace documentation"
2005 Sep 28
4
A document about implementing dtrace probes in SAX
Hi,
I have mentioned before that we have added some sdt dtrace probes in SAX,
our APL interpreter. Encouraged by Angelo and Jignesh, I have created a
small document (5 pages) describing our experience with it, together with
some problems we have encountered and some scripts we use for
pretty-printing dtrace outputs.
The said document can be found at
2006 Dec 07
2
System hangs when invoking DTrace script
Howdy,
I installed Nevada build 49 in a parallels VM on my intel mac mini,
and when I run the following DTrace script:
$ cat follow.d
#pragma option D flowindent;
pid$target:::entry,
pid$target:::return
{}
$ cat format.cmds
disk
0
exit
$ dtrace -s follow.d -o follow.out -c "/usr/sbin/format -f format.cmds"
dtrace: script ''follow.d'' matched 13641 probes
The system
2005 Nov 22
6
DTrace #include problems
Howdy,
I am trying to migrate several scripts to use application defined types,
and am running into a few issues. When I attempt to run a script with a
application defined type, it looks like the DTrace preprocessor is getting
angry with me:
$ cat view.d
#include "httpd.h"
:::acceptconnection
{
this->addr = (conn_rec *)copyin(arg0,sizeof(conn_rec *));
}
$ dtrace -C
2007 Apr 18
3
dtrace-discuss: cannot get a ''string'' to print...
hi,
I''m using the PID provider to trace a 32-bit app, prtdiag.
I''m trying to print the value of "propname" (arg1) in the
following func:
int
picl_get_propval_by_name(picl_nodehdl_t nodeh, const char *propname,
void *valbuf, size_t nbytes)
...
i''ve tried many versions, but this is a representative one:
53 this string propname;
54
55
2006 Mar 03
3
Using DTrace to locate memory leak
Howdy,
I am attempting to isolate the location of a memory leak in a 4GL program,
and have hit a bit of a snag. When I LD_PRELOAD libumem and run the
application server, "::findleaks -fdv" reports numerous leaks:
CACHE LEAKED BUFCTL CALLER
0000000100b49068 15 0000000100ef2d50 fdcon+0x6c4
0000000100b50028 1 0000000100b72ac0 fdcon+0x6c4
0000000100b49068
2007 Apr 27
6
User Privileges and Dtrace
Dear Experts,
My customer is migrating to Solaris 10 from Solaris 8 and have asked me to determine if: With Dtrace, is the user limited to probing only processes they own?
The customer has a general security requirement to control user access via management of privileges. Currently, on Solaris 8, LDAP is strongly while RBAC is weakly applied. This will likely change in the Solaris 10 production
2008 Jun 09
6
Dtrace on OpenSolaris/VirtualBox
I''m running OpenSolaris 2008.05 in VirtualBox on a Windows XP host. Playing around with various probes, I found that trying to load any probe associated with bdev_strategy dumps core.
I can think of one or two likely and reasonable causes for this, but am assuming it''s undesirable behavior.
Anyone know what''s happening here?
--
This message posted from
2006 Apr 07
1
dtrace: invalid probe specifier
Hello,
I''m a newby to dtrace and have just installed the dtrace toolkit v0.92 on
a core soalris 10 1/06 installation on SUN v40z.
I have tried the following commands:
iotop
iosnoop
but I get the message
dtrace: invalid probe specifier
and a lot of code. At the end it says:
: in action list: failed to resolve uid: Unknown variable name
Could it be, that there are some
2009 Sep 09
3
Dtrace and java 1.5
Hi,
I have used dtrace in the past for diagnosing IO/filesystem related issues.
So I am a bit familiar with dtrace scripts
Now I want to diagnose performance problems in the java area.
May be memory leak etc.
The hotspot provider is not present.
How can I get them?
Does someone have any further advice?
regards Hans
--
This message posted from opensolaris.org
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
2008 Feb 26
4
Why dtrace doesn''t work on some workstation?
Dtrace does work on some workstation, such as as follows,
-----------------------------------------------------------
bash-3.00# dtrace -s ./mem.d `pgrep test`
dtrace: script ''./mem.d'' matched 5 probes
^C
bash-3.00# uname -a
SunOS ftp 5.10 Generic_118833-17 sun4u sparc SUNW,Sun-Blade-100
bash-3.00# dtrace -V
dtrace: Sun D 1.1
2008 Aug 19
3
variables in dtrace scripts
Greetings,
is there a way to specify probes and other dtrace operations via command
line parameters, like
"
BEGIN
{
usr_exec=$$1;
usr_syscall=$$2;
}
syscall::usr_syscall:entry
/execname == usr_exec && guard++ == 0/
{
...
"
[this does not work]
This would make it possible to create "generic" dtrace scripts.
Otherwise, some shellscript with sed-magic would
2005 Oct 11
7
dtrace: failed to initialize dtrace: DTrace device not available on system
I have a number of systems running solaris10 and i see the package and binary for dtrace installed however whenever we try to run anything we get this error
dtrace: failed to initialize dtrace: DTrace device not available on system
the only system in which i dont have this error is the development server that has the full solaris 10 install while others are minimized, do i need additional
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
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 Apr 29
2
DTrace provider proposal: fibre channel (fc) COMSTAR port provider probes
I have added a specification of probes for the fibre channel COMSTAR
port provider to the DTrace section of wikis.sun.com. The proposal may
be found here: http://wikis.sun.com/display/DTrace/fibre+channel+Provider
I welcome feedback regarding this proposal.
Thanks,
Sam
2008 Oct 01
11
RFE: if/else control flow in probes
Hi all,
There''s a dead thread about this back at http://forums.sun.com/thread.jspa?threadID=5075157, but it would be really nice to have support for if/else control flow in actions.
Reasons:
1. The ternary operator ?: is already there (though it doesn''t let you do anything with side effects)
2. The user can already write arbitrary and expensive non-cacheable predicates if
2008 Jun 07
2
Apple fixes DTrace
I''m pleased to pass along news that the Mac OS X DTrace port has been
updated
in 10.5.3 to fix the issue that caused timer based probes not to fire
in the
presence of certain untraceable applications.
http://blogs.sun.com/ahl/entry/apple_updates_dtrace
A big thank you to the folks at Apple for addressing the problem.
Adam
--
Adam Leventhal, Fishworks
2008 May 16
2
how can we use libdtrace within the DTrace security restrictions?
Hi all,
What is the correct way to give one non-root user the ability to use
DTrace with providers running in a process by another user?
Through the Web Stack project and some work by Ludovic Champenois and
Nasser Nouri, we have done a bit of work to bring together parts of
chime, the Web Stack Apache, Ruby and PHP providers, and stuff reused
from the DTrace toolkit. It''s in
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