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
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 application, I get the following error message:
dtrace: invalid probe specifier pid93120:myApp::entry: failed
On May 7, 2010, at 6:10 PM, Eric Gorr wrote:
QUESTION #1:
I have defined three custom probes in my application. When I create a custom
instrument in Instruments to record when those probes fire, I do see them (
http://ericgorr.net/cocoadev/dtracetest_ins.trace.zip ).
However, when I
On May 10, 2010, at 6:15 PM, James McIlree wrote:
QUESTION #2:
Clearly, I can prevent DTrace from the command line from automatically
creating entry, etc. probes for my application.
So, the question then becomes, how can I tell DTrace that I want it to
automatically create entry, etc.
If it matters, I am using Mac OS X 10.6.x.
Let's say that I open a terminal window, enabled a few probes, and start
collecting data.
From a different terminal window can I ask DTrace what probes have been
enabled? If so, how?
Thank you.
___
symbol name
Some kernel symbols seem to be available; perhaps someone more
familiar with Mac OS X can get this script running over there.
Adam
On Tue, Jun 21, 2011 at 5:01 AM, Eric Gorr mail...@ericgorr.net wrote:
If it matters, I am using Mac OS X 10.6.x.
Let's say that I open
, 2011, at 4:12 PM, Eric Gorr wrote:
Thanks. This is quite interesting. I wonder where one goes to learn about
what kernel symbols are available in Mac OS X...?
On Jun 21, 2011, at 12:17 PM, Adam Leventhal a...@delphix.com wrote:
Hey Eric,
There's not a great way to do it, but you can use
So, I'm curious if you had an answer to the question of how one might be able
to determine what probes are enabled...?
If this is not possible on Mac OS x, I will go ahead and file a bug report.
Thank you
On Jun 22, 2011, at 3:14 PM, Steve Peters s...@mac.com wrote:
On Jun 22, 2011, at
Bug filed: rdar://9662467
On Jun 22, 2011, at 11:40 AM, Adam Leventhal wrote:
Steve, while we have you, can you explain why the dtrace_probes and
dtrace_nprobes variables aren't visible?
Adam,
It looks like our ctf_convert and/or ctf_merge casts (sic) a blind eye on
static data objects.
I can write a simple dtrace script to tell me each time the -orderOut: method
is called in my program.
#pragma D option quiet
objc$target::-orderOut?:entry
{
printf( %30s %10s %x %x\n, probemod, probefunc, arg0, arg1 );
}
I know that arg0 contains the address of self for the
10 matches
Mail list logo
