Solaris
-- on dtrace-disc...@lists.dtrace.org.
Adam
--
Adam Leventhal, Delphix
http://dtrace.org/blogs/ahl
275 Middlefield Road, Suite 50
Menlo Park, CA 94025
http://www.delphix.com
___
dtrace-discuss mailing list
dtrace-discuss@opensolaris.org
to kernel memory allowed in dtrace or not?
If so, anybody got a sample ?
thanks
wr
___
dtrace-discuss mailing list
dtrace-discuss@opensolaris.org
--
Adam Leventhal, Delphix
http://dtrace.org/blogs/ahl
275 Middlefield Road, Suite 50
Menlo
@opensolaris.org
--
Adam Leventhal, Delphix
http://dtrace.org/blogs/ahl
275 Middlefield Road, Suite 50
Menlo Park, CA 94025
http://www.delphix.com
___
dtrace-discuss mailing list
dtrace-discuss@opensolaris.org
to print probeprov, probemod and probefunc but
i prefer strjoin :)
In this case i doesn't understand where are syscall' count.
Anyone has an idea about this problem?
Cni
___
dtrace-discuss mailing list
dtrace-discuss@opensolaris.org
--
Adam
primitives.
Regards
Przemek
On Tue, Aug 09, 2011 at 09:01:59AM -0700, Adam Leventhal wrote:
Hi Przemyslaw,
It may be that the Oracle process doesn't use built-in locking
primitives. You can test that theory by doing this:
# dtrace -p pid -n 'plockstat$target:::{ @[probename] = count
___
dtrace-discuss mailing list
dtrace-discuss@opensolaris.org
--
Adam Leventhal, Delphix
http://dtrace.org/blogs/ahl
275 Middlefield Road, Suite 50
Menlo Park, CA 94025
http://www.delphix.com
___
dtrace-discuss mailing list
dtrace
-- though I would obviously welcome anyone else's
feedback as well!
- Bryan
___
Developer mailing list
develo...@lists.illumos.org
http://lists.illumos.org/m/listinfo/developer
--
Adam Leventhal, Delphix
http://dtrace.org/blogs/ahl
275
___
Developer mailing list
develo...@lists.illumos.org
http://lists.illumos.org/m/listinfo/developer
--
Adam Leventhal, Delphix
http://dtrace.org/blogs/ahl
275 Middlefield Road, Suite 50
Menlo Park, CA 94025
http://www.delphix.com
___
dtrace-discuss mailing list
dtrace-discuss@opensolaris.org
--
Adam Leventhal, Delphix
http://dtrace.org/blogs/ahl
275 Middlefield Road, Suite 50
Menlo Park, CA 94025
http://www.delphix.com
___
dtrace-discuss
--
Adam Leventhal, Delphix
http://dtrace.org/blogs/ahl
275 Middlefield Road, Suite 50
Menlo Park, CA 94025
http://www.delphix.com
___
dtrace-discuss mailing list
dtrace-discuss@opensolaris.org
their datatypes and those type definitions.
Adam
--
Adam Leventhal, Delphix
http://dtrace.org/blogs/ahl
275 Middlefield Road, Suite 50
Menlo Park, CA 94025
http://www.delphix.com
___
dtrace-discuss mailing list
dtrace-discuss@opensolaris.org
-discuss mailing list
dtrace-discuss@opensolaris.org
--
Adam Leventhal, Delphix
http://dtrace.org/blogs/ahl
275 Middlefield Road, Suite 50
Menlo Park, CA 94025
http://www.delphix.com
___
dtrace-discuss mailing list
dtrace-discuss@opensolaris.org
as
arg0 in entry.
I suspect I'm doing something wrong in dtrace but I can't realize
whatCould you please advice?
Regards
Andrea
___
dtrace-discuss mailing list
dtrace-discuss@opensolaris.org
--
Adam Leventhal, Delphix
http://dtrace.org
#!/usr/sbin/dtrace -I. -Cs
The kernel only picks up one argument from the #! line. You can use
#pragma incdir instead of the -I option.
Adam
--
Adam Leventhal, Delphix
http://dtrace.org/blogs/ahl
275 Middlefield Road, Suite 50
Menlo Park, CA 94025
http://www.delphix.com
%02x... To simplify it a little, you could cast it to a
uint64_t *:
printf(%16x%16x, ((uint64_t *)this-oinfo.xxx_id)[0], ((uint64_t
*)this-oinfo.xxx_id)[1]);
I hope that helps.
Adam
--
Adam Leventhal, Delphix
http://dtrace.org/blogs/ahl
275 Middlefield Road, Suite 50
Menlo Park, CA 94025
http
-discuss mailing list
dtrace-discuss@opensolaris.org
--
Adam Leventhal, Delphix
http://dtrace.org/blogs/ahl
275 Middlefield Road, Suite 50
Menlo Park, CA 94025
http://www.delphix.com
___
dtrace-discuss mailing list
dtrace-discuss@opensolaris.org
.
For the TCP stuff, take a look at Alan McGuire's work (hg version
501806a754d21dae2120629e8d705674877328f2) to figure out the relevant
functions to instrument with the fbt provider.
I hope that helps.
Adam
--
Adam Leventhal, Delphix
http://dtrace.org/blogs/ahl
275 Middlefield Road, Suite 50
Menlo
by default retuurns the module name
without the path. (libxyz.so)
Thanks
Vasanth
___
dtrace-discuss mailing list
dtrace-discuss@opensolaris.org
--
Adam Leventhal, Delphix http://dtrace.org/blogs/ahl
--
Adam Leventhal, Delphixhttp://dtrace.org/blogs/ahl
--
Adam Leventhal, Delphixhttp://dtrace.org/blogs/ahl
___
dtrace-discuss mailing list
dtrace-discuss@opensolaris.org
@opensolaris.org
--
Adam Leventhal, Delphix http://dtrace.org/blogs/ahl
___
dtrace-discuss mailing list
dtrace-discuss@opensolaris.org
with, say, the trace() action
(e.g. trace(stack());).
Arguably it's a bug that you can't use stack() in the way that you
described. You should feel free to file it with Oracle or in illumos.
Adam
--
Adam Leventhal, Delphixhttp://dtrace.org/blogs/ahl
unstable probes don't have semantic meanings that scripts can rely
upon.
Adam
--
Adam Leventhal, Delphix http://dtrace.org/blogs/ahl
___
dtrace-discuss mailing list
dtrace-discuss@opensolaris.org
to do?
Adam
--
Adam Leventhal, Delphix http://dtrace.org/blogs/ahl
___
dtrace-discuss mailing list
dtrace-discuss@opensolaris.org
and data collected from within a C++ program?
--
This message posted from opensolaris.org
___
dtrace-discuss mailing list
dtrace-discuss@opensolaris.org
--
Adam Leventhal, Delphix http://dtrace.org/blogs/ahl
--
Adam Leventhal, Delphixhttp://dtrace.org/blogs/ahl
___
dtrace-discuss mailing list
dtrace-discuss@opensolaris.org
I'm having a problem with USDT probes on FreeBSD. What probes should the
child process have when the parent is the one who installs USDT probes?
I see a problem with postgresql where drti.o installs the USDT probes but
then postgresql forks and the new child(s) don't install any new probes.
the process to continue.
Jim
--
This message posted from opensolaris.org
___
dtrace-discuss mailing list
dtrace-discuss@opensolaris.org
--
Adam Leventhal, Fishworkshttp://blogs.sun.com/ahl
*
args[1]: int
--
Shrikanth R K
--
This message posted from opensolaris.org
___
dtrace-discuss mailing list
dtrace-discuss@opensolaris.org
--
Adam Leventhal, Fishworkshttp://blogs.sun.com/ahl
___
dtrace-discuss mailing list
dtrace-discuss@opensolaris.org
--
Adam Leventhal, Fishworkshttp://blogs.sun.com/ahl
___
dtrace-discuss mailing list
dtrace-discuss@opensolaris.org
, but how does ld insert this section inside the ELF file?
Thanks,
--
Rui Paulo
___
dtrace-discuss mailing list
dtrace-discuss@opensolaris.org
--
Adam Leventhal, Fishworkshttp://blogs.sun.com/ahl
to understand the new section. Would it be reasonable
to do the same for GNU ld? Do you have a suggestion for how we might have
designed the interaction between DTrace and the linker differently?
Adam
--
Adam Leventhal, Fishworkshttp://blogs.sun.com/ahl
changes to the list and we'll get it reviewed.
Thanks.
Adam
Regards,
Ryan
On 7/19/2010 7:55 PM, Adam Leventhal wrote:
Hey Ryan,
We have special logic in pid provider entry and return probes to account for
the fact that they execute in leaf call context. Unfortunately
___
dtrace-discuss mailing list
dtrace-discuss@opensolaris.org
--
Adam Leventhal, Fishworkshttp://blogs.sun.com/ahl
___
dtrace-discuss mailing list
dtrace-discuss@opensolaris.org
___
dtrace-discuss mailing list
dtrace-discuss@opensolaris.org
___
dtrace-discuss mailing list
dtrace-discuss@opensolaris.org
--
Adam Leventhal, Fishworks http://blogs.sun.com/ahl
@opensolaris.org
--
Adam Leventhal, Fishworkshttp://blogs.sun.com/ahl
___
dtrace-discuss mailing list
dtrace-discuss@opensolaris.org
,
--
Rui Paulo
___
dtrace-discuss mailing list
dtrace-discuss@opensolaris.org
--
Adam Leventhal, Fishworkshttp://blogs.sun.com/ahl
___
dtrace-discuss mailing list
dtrace-discuss
of posting to the list
so the community can approve before updating the wiki.
Thanks, and apologies for the confusing behavior.
Adam
--
Adam Leventhal, Fishworkshttp://blogs.sun.com/ahl
___
dtrace-discuss mailing list
dtrace
);
self-follow = 0;
}
This applies both for user-land and the kernel.
Adam
--
Adam Leventhal, Fishworkshttp://blogs.sun.com/ahl
___
dtrace-discuss mailing list
dtrace-discuss@opensolaris.org
Michael,
Dtrace cannot instrument all return functions - I think it's got to do with
the way the stack is set up (I think leaf functions is the operative word
here, I may be wrong though).
I'd suggest you peruse the archives, Adam Leventhal among others has answered
this question
mailing list
dtrace-discuss@opensolaris.org
--
Adam Leventhal, Fishworkshttp://blogs.sun.com/ahl
___
dtrace-discuss mailing list
dtrace-discuss@opensolaris.org
@opensolaris.org
--
Adam Leventhal, Fishworkshttp://blogs.sun.com/ahl
___
dtrace-discuss mailing list
dtrace-discuss@opensolaris.org
= timestamp - self-t[probefunc] ;
@[probefunc] = avg(this-time) ;
self-t[probefunc] = 0 ;
}
___
dtrace-discuss mailing list
dtrace-discuss@opensolaris.org
--
Adam Leventhal, Fishworkshttp://blogs.sun.com/ahl
://wikis.sun.com/display/DTrace/kerberos+Provider
I'd like to submit the PSARC case for this soon so I'm setting the
deadline for comments to Monday April 3rd.
Thanks,
-M
___
dtrace-discuss mailing list
dtrace-discuss@opensolaris.org
--
Adam
over 50 OR clauses !
Thanks
Angelo
___
dtrace-discuss mailing list
dtrace-discuss@opensolaris.org
--
Adam Leventhal, Fishworkshttp://blogs.sun.com/ahl
___
dtrace-discuss
idea why dtrace stops tracing, as if the ring policy was not applied ?
Cheers,
Philippe Magerus
___
dtrace-discuss mailing list
dtrace-discuss@opensolaris.org
--
Adam Leventhal, Fishworkshttp://blogs.sun.com/ahl
I have the core file if anyone is interested.
The issue is fully reproducible.
___
dtrace-discuss mailing list
dtrace-discuss@opensolaris.org
--
Adam Leventhal, Fishworkshttp://blogs.sun.com/ahl
@opensolaris.org
--
Adam Leventhal, Fishworkshttp://blogs.sun.com/ahl
___
dtrace-discuss mailing list
dtrace-discuss@opensolaris.org
with
tracemem, I consistently get invalid address for all door_calls.
Remember that if you're trying to trace memory from user-land you'll have to do
a copyin(). For example:
tracemem(copyin(arg0, 64), 64);
Adam
--
Adam Leventhal, Fishworkshttp://blogs.sun.com/ahl
/
iEYEARECAAYFAkqfLusACgkQx0z2pBWsSnOiVACgnsBgrj0c2lkIVgKt816pJkEJ
iYIAnidChUSqPHEuF7ALdHtuKfADV79q
=H5jP
-END PGP SIGNATURE-
___
dtrace-discuss mailing list
dtrace-discuss@opensolaris.org
--
Adam Leventhal, Fishworkshttp://blogs.sun.com/ahl
. Is there any work around?
Thanks,
Bob
--
This message posted from opensolaris.org
___
dtrace-discuss mailing list
dtrace-discuss@opensolaris.org
--
Adam Leventhal, Fishworkshttp://blogs.sun.com/ahl
more appropriate for the ZFS discussion list, but, no, there is
no plan for multiple active writers for example.
Adam
--
Adam Leventhal, Fishworkshttp://blogs.sun.com/ahl
___
dtrace-discuss mailing list
dtrace-discuss
after the #!
syntax. Also note that -Z should only be used if its known that the probes
specified will show up at some later time -- otherwise you'll never see
any output.
Adam
--
Adam Leventhal, Fishworkshttp://blogs.sun.com/ahl
I'd follow up to see if there is any progress on this issue:
a static library and an application cannot currently provide USDT
probes simultaneously?
There is no progress on this issue. I suggest you find the relevant
bug and add a call record.
Adam
--
Adam Leventhal, Fishworks
in sigaction?
___
dtrace-discuss mailing list
dtrace-discuss@opensolaris.org
--
Adam Leventhal, Fishworkshttp://blogs.sun.com/ahl
___
dtrace-discuss mailing list
dtrace-discuss@opensolaris.org
from opensolaris.org
___
dtrace-discuss mailing list
dtrace-discuss@opensolaris.org
--
Adam Leventhal, Fishworkshttp://blogs.sun.com/ahl
___
dtrace-discuss mailing list
dtrace-discuss
___
dtrace-discuss mailing list
dtrace-discuss@opensolaris.org
--
Adam Leventhal, Fishworkshttp://blogs.sun.com/ahl
___
dtrace-discuss mailing list
dtrace-discuss@opensolaris.org
_start:entry
37 59614 _start:entry
thanks
--
This message posted from opensolaris.org
___
dtrace-discuss mailing list
dtrace-discuss@opensolaris.org
--
Adam Leventhal, Fishworkshttp://blogs.sun.com/ahl
___
dtrace-discuss mailing list
dtrace-discuss@opensolaris.org
--
Adam Leventhal, Fishworkshttp://blogs.sun.com/ahl
___
dtrace-discuss mailing list
dtrace-discuss@opensolaris.org
Any method to use the PID provider on a group of processes?(tasks/
projects etc) other than separate invocations.
Unfortunately, there isn't.
Adam
--
Adam Leventhal, Fishworkshttp://blogs.sun.com/ahl
___
dtrace-discuss
I like to trace the original instruction also is it possible?
This isn't possible. It was filed a long time ago as a low priority RFE:
5106439 pidprovider instrumentation obscures original instruction
Adam
--
Adam Leventhal, Fishworkshttp://blogs.sun.com/ahl
keeps running, it becomes useless
after some time on such a heavily loaded system.
--
This message posted from opensolaris.org
___
dtrace-discuss mailing list
dtrace-discuss@opensolaris.org
--
Adam Leventhal, Fishworkshttp
is there perhaps something like a dtrace course?
I want to dtrace java with djvm/dvm Provider .
Regards Hans-Peter
-Original Message-
From: Adam Leventhal [mailto:a...@eng.sun.com]
Sent: Friday, September 11, 2009 20:31
To: Sloot, Hans-Peter
Cc: dtrace-discuss@opensolaris.org
Subject: Re: [dtrace
the dvm or djvm providers.
Regards Hans
--
This message posted from opensolaris.org
___
dtrace-discuss mailing list
dtrace-discuss@opensolaris.org
--
Adam Leventhal, Fishworkshttp://blogs.sun.com/ahl
the
output you're seeing? Can you describe the change you're seeing that you
believe to be in error?
Adam
--
Adam Leventhal, Fishworks http://blogs.sun.com/ahl
___
dtrace-discuss mailing list
dtrace-discuss@opensolaris.org
a cache of compiled code or once compiled is the native
code fairly static?
Adam
--
Adam Leventhal, Fishworks http://blogs.sun.com/ahl
___
dtrace-discuss mailing list
dtrace-discuss@opensolaris.org
Hi Joel,
Has anyone tried to access member fields of C++ objects from within
DTrace?
Can this be done?
It can be done, but not easily. You'll need to figure out the byte
offset
and manually pull out the member.
Adam
--
Adam Leventhal, Fishworkshttp
What is the alternative then?
As I said: find the byte offsets for the members you're interested in.
Adam
--
Adam Leventhal, Fishworks http://blogs.sun.com/ahl
___
dtrace-discuss mailing list
dtrace-discuss@opensolaris.org
there forever.
Adam
--
Adam Leventhal, Fishworks http://blogs.sun.com/ahl
___
dtrace-discuss mailing list
dtrace-discuss@opensolaris.org
.
___
dtrace-discuss mailing list
dtrace-discuss@opensolaris.org
___
dtrace-discuss mailing list
dtrace-discuss@opensolaris.org
--
Adam Leventhal, Fishworkshttp://blogs.sun.com/ahl
::CFRetain:entry
/this-classname == CALayer/
{
trace(CFRetain(CALayer));
}
Hope that helps.
Adam
--
Adam Leventhal, Fishworkshttp://blogs.sun.com/ahl
___
dtrace-discuss mailing list
dtrace-discuss@opensolaris.org
--
Adam Leventhal, Fishworkshttp://blogs.sun.com/ahl
___
dtrace-discuss mailing list
dtrace-discuss@opensolaris.org
___
dtrace-discuss mailing list
dtrace-discuss@opensolaris.org
--
Adam Leventhal, Fishworkshttp://blogs.sun.com/ahl
___
dtrace-discuss mailing list
dtrace-discuss@opensolaris.org
systems.
It's possible that there was some bug in a Solaris 10 update, but there's
nothing that should make this happen. Please find out exactly what version
the user is running along with any patches. Further, it would be useful to
see the output of 'dtrace -lv -n sched:::change-pri'.
Adam
--
Adam
of the string being copied
in. For
example, calls to write(2) obviously don't need to use null-terminated
strings so the following takes this into account:
syscall::write:entry
{
trace(copyinstr(arg1, arg2));
}
Adam
--
Adam Leventhal, Fishworkshttp://blogs.sun.com
dtrace-discuss@opensolaris.org
--
Adam Leventhal, Fishworkshttp://blogs.sun.com/ahl
___
dtrace-discuss mailing list
dtrace-discuss@opensolaris.org
+Provider
Some of the examples in that chapter will be instructional.
Adam
--
Adam Leventhal, Fishworkshttp://blogs.sun.com/ahl
___
dtrace-discuss mailing list
dtrace-discuss@opensolaris.org
.
That's correct. What was the failure mode? We could at least emit a
helpful
message.
Adam
--
Adam Leventhal, Fishworkshttp://blogs.sun.com/ahl
___
dtrace-discuss mailing list
dtrace-discuss@opensolaris.org
of
expertise with dtrace development,I would like it to know whether it
can be done or not?
Thanks a lot.
With Regards,
Abhinav.
___
dtrace-discuss mailing list
dtrace-discuss@opensolaris.org
--
Adam Leventhal, Fishworkshttp
. It
appears that there's something broken about the iscsit.d file. This is a bug
in Solaris. You can problem work around the problem by moving that file
aside.
Adam
--
Adam Leventhal, Fishworks http://blogs.sun.com/ahl
___
dtrace-discuss
The error I am getting is:
operator - cannot be applied to a forward declaration: no struct
proc_t definition is available
You need to use the same syntax as in C. This means either 'proc_t' or
'struct proc'.
Adam
--
Adam Leventhal, Fishworkshttp://blogs.sun.com
.
--
This message posted from opensolaris.org
___
dtrace-discuss mailing list
dtrace-discuss@opensolaris.org
--
Adam Leventhal, Fishworkshttp://blogs.sun.com/ahl
___
dtrace-discuss mailing list
I be fixing this some other way?
Chad
___
dtrace-discuss mailing list
dtrace-discuss@opensolaris.org
--
Adam Leventhal, Fishworkshttp://blogs.sun.com/ahl
___
dtrace-discuss mailing
: syntax error near )
This suggests that dtrace doesn't know what fcp_pkt type is. I followed
this up with...
I think you want to do '(struct fcp_pkt *)' rather than '(fcp_pkt *)' just
as you would in C.
Adam
--
Adam Leventhal, Fishworks http://blogs.sun.com/ahl
-discuss mailing list
dtrace-discuss@opensolaris.org
--
Adam Leventhal, Fishworkshttp://blogs.sun.com/ahl
___
dtrace-discuss mailing list
dtrace-discuss@opensolaris.org
@opensolaris.org
--
Adam Leventhal, Fishworks http://blogs.sun.com/ahl
___
dtrace-discuss mailing list
dtrace-discuss@opensolaris.org
@opensolaris.org
--
Adam Leventhal, Fishworks http://blogs.sun.com/ahl
___
dtrace-discuss mailing list
dtrace-discuss@opensolaris.org
Considerations chapter.
--
This message posted from opensolaris.org
___
dtrace-discuss mailing list
dtrace-discuss@opensolaris.org
--
Adam Leventhal, Fishworks http://blogs.sun.com/ahl
|0|UNDEF
|__dtrace_probe___vtrace_TR_RFSCALL_END
[1586] | 0| 0|FUNC |GLOB |0|UNDEF
|__dtrace_probe___vtrace_TR_RFSCALL_START
...
Adam
--
Adam Leventhal, Fishworks http://blogs.sun.com/ahl
___
dtrace-discuss
dtrace-discuss@opensolaris.org
--
Adam Leventhal, Fishworkshttp://blogs.sun.com/ahl
___
dtrace-discuss mailing list
dtrace-discuss@opensolaris.org
dtrace-discuss@opensolaris.org
--
Adam Leventhal, Fishworkshttp://blogs.sun.com/ahl
___
dtrace-discuss mailing list
dtrace-discuss@opensolaris.org
of explicit atomic operation for global variables,
but
in the vast majority of cases, aggregations are the right answer.
Adam
--
Adam Leventhal, Fishworkshttp://blogs.sun.com/ahl
___
dtrace-discuss mailing list
dtrace-discuss
variables.
Adam
--
Adam Leventhal, Fishworks http://blogs.sun.com/ahl
___
dtrace-discuss mailing list
dtrace-discuss@opensolaris.org
.
Adam
--
Adam Leventhal, Fishworks http://blogs.sun.com/ahl
___
dtrace-discuss mailing list
dtrace-discuss@opensolaris.org
in a tick probe.
Hi Andrew,
Take a look at the documentation for aggregations: that's the mechanism you
want to use for what you describe above.
Adam
--
Adam Leventhal, Fishworks http://blogs.sun.com/ahl
___
dtrace-discuss mailing
, all ?
-- Forwarded message --
From: Amit Saha amitsaha...@gmail.com
Date: 2009/3/26
Subject: Custom macros in USDT probes
To: Adam Leventhal a...@eng.sun.com
Hello Adam,
In http://www.solarisinternals.com/wiki/index.php/DTrace_Topics_USDT#USDT_Macros
,
its mentioned that its
of
a potential lock ordering
issue?
James M
___
dtrace-discuss mailing list
dtrace-discuss@opensolaris.org
--
Adam Leventhal, Fishworkshttp://blogs.sun.com/ahl
___
dtrace
andrea.cuccia...@sun.com
___
dtrace-discuss mailing list
dtrace-discuss@opensolaris.org
--
Adam Leventhal, Fishworkshttp://blogs.sun.com/ahl
___
dtrace-discuss mailing list
dtrace-discuss
it?
In this case were are talking about the dtrace extension of php
distributed with OpenSolaris.
Hey David,
Sorry about that. Please file a bug if you haven't already.
Adam
--
Adam Leventhal, Fishworks http://blogs.sun.com/ahl
project if anyone's
interested
in taking a crack at it.
Adam
--
Adam Leventhal, Fishworkshttp://blogs.sun.com/ahl
___
dtrace-discuss mailing list
dtrace-discuss@opensolaris.org
___
dtrace-discuss mailing list
dtrace-discuss@opensolaris.org
--
Adam Leventhal, Fishworkshttp://blogs.sun.com/ahl
___
dtrace-discuss mailing list
dtrace-discuss@opensolaris.org
1 - 100 of 281 matches
Mail list logo