Re: [dtrace-discuss] What does this DTrace error mean?
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 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 debug build of my application, when I execute: sudo dtrace -l -n 'pid93120:myApp::entry' I get a nice long list of entry probes, including one for -[NNASoundManager initializeSounds] : 154562 pid82065 myApp -[NNASoundManager initializeSounds] entry Does anyone know what might be causing this error and how to get around it? I have been able to get the list of entry probes for the release build of a test application...it is just unclear to me where to look for differences that might affect this. Thank you. ___ dtrace-discuss mailing list dtrace-discuss@opensolaris.org ___ dtrace-discuss mailing list dtrace-discuss@opensolaris.org
Re: [dtrace-discuss] What does this DTrace error mean?
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 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 to create entry probe for '-[NNASoundManager initializeSounds]': Invalid argument For the debug build of my application, when I execute: sudo dtrace -l -n 'pid93120:myApp::entry' I get a nice long list of entry probes, including one for -[NNASoundManager initializeSounds] : 154562 pid82065 myApp -[NNASoundManager initializeSounds] entry Does anyone know what might be causing this error and how to get around it? I have been able to get the list of entry probes for the release build of a test application...it is just unclear to me where to look for differences that might affect this. ___ dtrace-discuss mailing list dtrace-discuss@opensolaris.org
Re: [dtrace-discuss] What does this DTrace error mean?
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 PM, James McIlree wrote: 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 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 debug build of my application, when I execute: sudo dtrace -l -n 'pid93120:myApp::entry' I get a nice long list of entry probes, including one for -[NNASoundManager initializeSounds] : 154562 pid82065 myApp -[NNASoundManager initializeSounds] entry Does anyone know what might be causing this error and how to get around it? I have been able to get the list of entry probes for the release build of a test application...it is just unclear to me where to look for differences that might affect this. ___ dtrace-discuss mailing list dtrace-discuss@opensolaris.org
