DTrace on Leopard: No probes specified, even when I specify probes


DTrace on Leopard: No probes specified, even when I specify probes



% sudo dtrace -p 2446 'objc$target:NSObject:-init:entry { trace(); }' dtrace: no probes specified 

The manpage suggests that this is the correct format with which to specify a probe on an Objective-C method. I tried -Z, but (unsurprisingly) that just didn't print anything.

[Added] It's not even specific to Objective-C probes. I tried it with a C function from AppKit:

sudo dtrace -p 2446 'pid$target::NSPopAutoreleasePool:entry { trace(); }' dtrace: no probes specified 

So what's wrong? Why does DTrace think I have not specified any probes?


Is releasing memory of Objective-c 2.0 properties required?

1:

Requesting a callback using selectors
I think you mean:. Who owns an NSWindowController, in standard practice?
sudid  dtrace -p 2446 -n 'objc$tarreceive :NSObject:-init:entry { trace(); }' 
Cocoa Applications ExamplesNSTableView doesn't increase the number of elements in table?

2:

Cocoa Base 64 Implementation for REST Auth
In addition to what Graham said, your original statement will only find instances of NSObject, not its descendents. Cocoa Data Manipulation You could try. Carbon development on intel based mac
sudid  dtrace -p 2446 -n 'objc$tarreceive ::-init*:entry {}' 
to catch all -init variants by all NSObject-derived instances..

3:

Does the process in question allow dtrace? Apple doesn't always allow dtrace on os x..


98 out of 100 based on 53 user ratings 808 reviews

^