Hi
I wonder if I can use a printa statement with a format string to print a
quantize aggregation (that is, a histogram), and if so, what flag should I be
using in the format string for the histogram.
In particular, I'm interested in using a single printa statement to print
multiple
First, I am using Mac OS X 10.6.3. I am still fairly new to DTrace.
For the release build of my application, I get the following error message:
dtrace: invalid probe specifier pid93120:myApp::entry: failed to create entry
probe for '-[NNASoundManager initializeSounds]': Invalid argument
For
Eric,
What is the dtrace command you were using when you got the error you're
seeing against the release build?
James M
On May 7, 2010, at 9:13 AM, Eric Gorr wrote:
First, I am using Mac OS X 10.6.3. I am still fairly new to DTrace.
For the release build of my
Oh, sorry, I should have made that more clear...the same one I executed on the
debug build:
sudo dtrace -l -n 'pid93120:myApp::entry'
On May 7, 2010, at 1:37 PM, James McIlree wrote:
Eric,
What is the dtrace command you were using when you got the error you're
seeing against the
Can you rerun with -xdebug and email me the output?
James M
On May 7, 2010, at 10:39 AM, Eric Gorr wrote:
Oh, sorry, I should have made that more clear...the same one I executed on
the debug build:
sudo dtrace -l -n 'pid93120:myApp::entry'
On May 7, 2010, at 1:37
I have a very simple dtrace script ( shown below ).
This script works on simple programs just fine.
Now I want to use this script on a large C++ executable.
The executable is 8.5 meg in size on a x86 platform.
This executable has more than 10 threads in it.
I try to execute that the
Hey William,
There are a variety of reasons why dtrace(1M) would be unable to grab the
process -- for example, if the process you identified doesn't exist or if you
don't have permissions to it. Try this:
truss -t open dtrace -s adc.d 24930
... you might see output like this:
...
Hi
I'm using a single printa statement to print multiple aggregations, and I would
like to only show the N lines with the highest value for one of the printed
columns. E.g:
printa(%d %...@d %...@d\n, @totalCost, @totalOccurrences);
and I would like to show the 10 lines with the highest
Hello,
How can I access frame pointer? I am trying to get a variable value. Here is
the disassembly of the function.
function+0x208:st%l0, [%fp - 0xc]
I am trying to the value at [%fp - 0xc]
Thanks
--
This message posted from opensolaris.org
On Fri, May 07, 2010 at 12:38:02PM -0700, tester wrote:
Hello,
How can I access frame pointer? I am trying to get a variable value. Here is
the disassembly of the function.
function+0x208:st%l0, [%fp - 0xc]
I am trying to the value at [%fp - 0xc]
You can access the
It doesn't appear to be documented, but it appears that uregs[R_FP]
will give you the value. (At least on SPARC, you'll need to know
which register the FP is stored in on x86.)
Chad
On Fri, May 7, 2010 at 3:38 PM, tester solaris.ident...@gmail.com wrote:
Hello,
How can I access frame
On May 7, 2010, at 11:41 AM, Eric Gorr wrote:
Again, I am using Mac OS X 10.6.3.
First, I am curious, how is DTrace getting the function name information for
a release build when all of it's symbols have been stripped from it and there
is not dSym file either in the application
On Fri, May 07, 2010 at 12:56:25PM -0700, tester wrote:
Do I need to add stack bias 2047to fp to get actual data?
On 64-bit SPARC, yes.
Nico
--
___
dtrace-discuss mailing list
dtrace-discuss@opensolaris.org
On Fri, May 7, 2010 at 3:56 PM, tester solaris.ident...@gmail.com wrote:
Thanks.
Do I need to add stack bias 2047to fp to get actual data?
which is correct?
printf(localvar value is %x\n, (uregs[R_I6]));
or
printf(localvar value is %x\n, uregs[R_I6] + 2047);
I don't think you need to
I tripped over this bug recently.
Has anyone ever attempted to fix this?
- Bill
___
dtrace-discuss mailing list
dtrace-discuss@opensolaris.org
Chad/Nico,
Thank you for your help
--
This message posted from opensolaris.org
___
dtrace-discuss mailing list
dtrace-discuss@opensolaris.org
# dtrace -n
'pid$target::a:18{tracemem(copyin(uregs[R_FP] - 8, 64), 64)}' -c ./a.out
Hello Chad,
Why do you need to subtract 8 from FP? Thanks
--
This message posted from opensolaris.org
___
dtrace-discuss mailing list
dtrace-discuss@opensolaris.org
17 matches
Mail list logo
