I get an error message:
dtrace: failed to compile script gorillatrace.d: line 4: invalid probe description “objc$1:Carthage_EAGLView:-renderWithSquareVertices?textureVertices?:entry”: Undefined macro variable in probe description
However, if I replace the name of the class (Carthage_EAGLView) with ‘target’ -->
DTrace can be a bit twitchy with the objc provider - if you supply a class name (without wildcards), and the method is in a category, the probe descriptions won’t match.
Get a listing of all the available objc probes with:
results in this error: dyld: Library not loaded: /System/Library/Frameworks/OpenGLES.framework/OpenGLES
Referenced from: /Users/toddbarker2002/Library/Developer/Xcode/DerivedData/Athens-bizdhmbleqcmmndbevbzdnftynfw/Build/Products/Release-iphonesimulator/Athens.app/Athens
Reason: image not found
dtrace: failed to control pid 11561: process exited with status 0
Does dtrace need a path to my frameworks even if the app runs ok in the simulator? If so where would I insert in the dtrace command?
Ah, didn’t know it was for the simulator. Since it’s not really a runnable program dtrace can’t load it directly (at least that’s my theory). So you’ll need to catch it when running. Assuming the app named ‘Blah’, and running in the simulator
I can really see the power in dtrace … With all the data available (especially the statistics) you could write your
own custom performance tool and use in real time